Page 1 of 1
hardcoding the dim elements in the feeders
Posted: Tue Apr 19, 2011 5:50 am
by BigG
Hi,
I have a cube without a dim 'Year' feeding a cube with the dim 'Year'. The 'Year' is a single list (no rollups) leaf node only.
Without hardcoding the year in the feeders, does anyone have a suggestion on how to dynamically feed the year?
eg. dont want to hardcode 2012,2013,2014 as per below
Code: Select all
['Position Status' , 'Current' ] =>DB('Recovery', '2012', !Branches, 'Current' , !Employee , 'Position Status');
['Position Status' , 'Current' ] =>DB('Recovery', '2013', !Branches, 'Current' , !Employee , 'Position Status');
['Position Status' , 'Current' ] =>DB('Recovery', '2014', !Branches, 'Current' , !Employee , 'Position Status');
THanks in advance...g
Re: hardcoding the dim elements in the feeders
Posted: Tue Apr 19, 2011 6:16 am
by Gregor Koch
Hi
You could create a consolidation in the Year dimension which (only) contains the years you want to feed and refer to that in the feeder.
Note that feeders won't be re-fired if you add an element to that consolidation, so it is not dynamic in that way. You would have to re-process (rule save or cubeprocessfeeders('cubename') in TI)the feeders in that case.
Cheers
Re: hardcoding the dim elements in the feeders
Posted: Tue Apr 19, 2011 12:29 pm
by jim wood
You could also do a variable feeder if your feeling brave. Create a control containing the current year and put an if statement in the DB part of the feeder so it will only ever feed the current year.
Also does this need to be dynamic? Could you complete a copy to the year using TI? It might improve performance a little,
Jim.
Re: hardcoding the dim elements in the feeders
Posted: Tue Apr 19, 2011 11:30 pm
by BigG
Hi thanks for responses Jim and Gregor,
looks like a rollup for the Year dim then.
Note that feeders won't be re-fired if you add an element to that consolidation, so it is not dynamic in that way. You would have to re-process (rule save or cubeprocessfeeders('cubename') in TI)the feeders in that case
Did not know this was required for changing a dimnension structure for feeders targetting consolidated items. though it was only if you modify the rule in a TurboIntegrator process? Does AddCubeDependency do the same job?
variable feeder if your feeling brave
Needs to be 5 years of feeders, not just the one,
need to be dynamic? Could you complete a copy to the year using TI?
Most the model is TI process managed, have this small cube running on rules as it is relatively small and lends towards a 'realtime' requirement...
Re: hardcoding the dim elements in the feeders
Posted: Wed Apr 20, 2011 5:24 am
by Gregor Koch
Hi
[/quote] Did not know this was required for changing a dimnension structure for feeders targetting consolidated items. though it was only if you modify the rule in a TurboIntegrator process? Does AddCubeDependency do the same job?
quote]
As far as I know the AddCubeDependency does not refire feeders, it only tells the system that there is a dependency between two cubes so it does not need to establish it during run time (if not identified already at start up).
What I meant is that if your data in the source does not change, adding an element to your 'feeding'-consolidation won't automatically refire feeders to that new element. Only subsequent changes in your source cube (if numeric, from zero to a number) will also feed the new element or.... see above.
Cheers