Feeder Issue

[mce]

Hi,

I have a rule in cube B to pull values from cube A.
Accordingly I have feeders in cube A to feed required calculations in cube B.
However, some of the cells are not calculated in B, while most other are calculated properly although they are subject to the same rule and same feeder.
For the cells which are not properly calculated in cube B, when I checked the Check Feeders, I cannot see that the cell is being fed from cube A.
However when I do a Trace Feeders from the source cells in cube A, it shows that the cells in cube B are properly fed.
When I do a Check Formula in those cells in cube B, I can see the correct formula, but does not display that the formula is calculated properly.

What might be the cause of the issue?

Thanks in advance for the responses.

Regards,

[Neil Watson]

Hello there,

If we assume that the feeders you have written to feed cube B are correct, then its most likely that the data from which you are feeding is not fed.

So I would check that the source data in cube A is fed. This is why it's always preferable to feed from an input cell where possible.

Just a pointer to start things off.

Enjoy your journey into the world of feeders, it's only just beginning......

If this doesn't point you in the right direction, then post a copy of the rules, and we'll have a further look.

HTH
Neil

[mce]

Thanks for the response.
Found the issue.
rule was using the name alies, while feeder was using the code alies for one of the dimensions.
As the names were different in boh dimensions for some items altough the codes are the same, the rule did not work for those cells although feeder was correct.
I changed the rule to use the code alies and it fixed the problem.

[lotsaram]

You are better off to use element principal names only in rules and feeders. If you use an alias then although the rule may well compile and work correctly (and may well be easier to read) should the alias values change then your rule will break silently and invalidate the entire rule file for the cube. Should this happen finding the culprit rule line can be like finding the proverbial needle in a haystack. Better to make sure in your design that this can never happen.