Intercube Feeders

[Goatship]

Dear Steve Rowe,

You mean the essence of feeders is to tell if this number exist in the feeding cell, go check the rule of the fed cell.

For example;

A =>B

means
if A = 0, then skip rule checking of B. If A <>0, go perform rules of B

Therefore we can ignore how the rules are written in writing feeders. Is this correct?
If true this would be a lot of help in case the rules are very complex.

Thanks a lot.

NO.
But you are on the right track sort of. The purpose of the feeder is to tell the consolidation engine which values to aggregate. If you happen to query a specific cell (or a number of cells in a view array) then the calculation engine will still evaluate the indivdual value in each rule defined cell correctly. It is just that without feeders these values will not aggregate whihc leads to incorrect results at higher levels of the hierarchy.

It is true that the feeder does not have to reflect the rule (it is just that most of the time it does.)

I have tried feeding, A=>B, A and B are both in cube1; based on the reasoning that whenever A has value, B has value.
But it does not work, because when I take "A" to be part of another rule, the rule does not perform (the ruled cell does not even appear as grey color).

The problem is I could not feed the rule, which goes like this,
Cube1: dimension Grade Level (1,2,3)
Cube2: dimension Position (A,B,C,D,E,F), with numeric attribute of Grade Level named 'Grade Number'
dimension Measure, one of the measure is "Grade Level" with rule Grade Level = attrn('Grade Number')
At Cube2
pattern1: []= DB (Cube1,..., DB(Cube2,!Position,...,'Grade Level') ,.....)
or, which results in the same thing,
pattern2: []= DB(Cube1,..., attrn(!Position,Grade Number') ,.......)
At Cube1
[]=>DB(Cube2,....Here is the problem!!
How do we refer to dimension Position in Cube2, in relation to dimension Grade Level in Cube1
We could not create attributes at Grade Level dimension of Cube1, because one Grade Level has many positions.
Nor referring to attribute "Grade Number" of dimension Position in Cube2, even if attribute is Alias type
also not working is, referring to Measure Grade Level with the DB inside DB, (similar to "pattern2") with the !Position

I have tried plain way, feeding to !Position, but seems the server could not handle it, because Position dimension is heavy, like 700 elements.
Any ideas on a way to feed that save up memory?

[Christopher Kernahan]

Hi Goatship,

If you put the rules from both the cubes in your post it might help in diagnosing what's wrong.

[tomok]

The purpose of feeders is to tell TM1 which cells, that are subject to rule calculations, will actually evaluate to something other than 0. In your example it looks like Cube1 is really just a lookup cube for determining what a person's grade level is. Why would you use the existence of grade level data as a feeder for Cube2??? Isn't headcount the actual determining factor as to whether or not any data exists for a particluar grade level? You should feed from whatever cube has the headcount data. Since you've only given us partial code in your example I can't tell where that is but it's probably in Cube2. If it is then you don't need an intercube feeder at all.

[Goatship]

Thanks all! This morning I have tried commenting out the skipcheck, and it didnt work so it is not even becuz of feeders. The rule with one string value did not process, after a few attempt of change around it did process. dunno what actually happened. -_-'