TM1 Forum

Hi guys,
I don't think I have discovered a wheel but I just wanted to share (and hopefully confirm) my thoughts...

We are using conditional feeders for some specific things such as feeding budget versions with actuals only for specific periods of time, feeding only specific measures etc.

I know that when using conditional feeders with attributes we have to re-fire feeders manually in case of attribute change. The another approach for this is to create a config cube where attributes/parameters will be stored and we can use this cube as the condition for the feeders.

I think that using config cubes is better for conditional feeders as when there is a change in the data within the config cube the feeder is re-fired automatically.

I appreciate your opinions guys!

BR
Vladino

vladino wrote:I think that using config cubes is better for conditional feeders as when there is a change in the data within the config cube the feeder is re-fired automatically.

Better than what? Using an attribute? That would not be a correct statement since an attribute is nothing more than a value stored in a special cube. Feeding from an }ElementAttributes cube versus some cube you created for yourself would not be any different with the exception that your cube could contain more dimensions possibly making the feeder code more efficient. I say possibly because I don't know your design or coding. Also, you would need to define a "change". Going from nothing to something in the cell will fire feeders but simply changing a value will not and you'll have to re-fire manually.

I know that when using conditional feeders with attributes we have to re-fire feeders manually in case of attribute change. The another approach for this is to create a config cube where attributes/parameters will be stored and we can use this cube as the condition for the feeders.

As Tomok said, we'd need to know more about what you're attempting to pinpoint the precise issue. However, there are a couple of issues that pop up based on what you've asked.

If you are using the attribute to address the feeder (DB(cubename, attrvalue, ...) then changing the attribute will never fire the feeder. The feeder would have to be based on the attribute itself. ['attribute'] => DB(cubename, attrvalue, ...) which may be tough to avoid overfeeding or have a really ugly looking feeder.

The only way I know of to have a feeder re-fire (within the model, not reprocessing feeders/saving rules/etc) is to feed from string value. When a string value changes and it is being used to feed, the feeder will re-fire, and you can structure that feeder to take advantage of any addressing changes for the feeder.

PavoGa wrote:

The only way I know of to have a feeder re-fire (within the model, not reprocessing feeders/saving rules/etc) is to feed from string value. When a string value changes and it is being used to feed, the feeder will re-fire, and you can structure that feeder to take advantage of any addressing changes for the feeder.

Suppose i have following rule in the model:

Feeder;

['May (4+8) Forecast']=N:IF((DB('1f_Rollover Flag',!MetroLocation,'May (4+8) Forecast',!Accounts,!1t_Months,'Flag Value')=(1)),
DB(IF(DB('1f_Admin','Current Fcst Version','Version - Month View')@='May (4+8)','DataInputCube',''),!MetroLocation,'Actual - Current Year',!Accounts,!1t_Months),
DB(IF(DB('1f_Admin','Current Fcst Version','Version - Month View')@='May (4+8)','DataInputCube',''),!MetroLocation,'Manual Forecast',!Accounts,!1t_Months));

Skipcheck;

['Manual Forecast']=>DB(IF(DB('1f_Admin','Current Fcst Version','Version - Month View')@='May(4+8)','DataInputCube',''),!MetroLocation,'May(4+8)',!Accounts,!1t_Months);

Now if i change the value in "1f_admin" cube from Apr (3+9) to May (4+8) then would all feeders be recalculated?

Thanks,

Dharav

No because your feeder is in 'DataInputCube'; when you change a value in '1f_admin' it has no way of knowing that it needs to reevaluate and fire feeders in 'DataInputCube' without you somehow telling it to.

declanr wrote:No because your feeder is in 'DataInputCube'; when you change a value in '1f_admin' it has no way of knowing that it needs to reevaluate and fire feeders in 'DataInputCube' without you somehow telling it to.

Except manually re-fire the feeders, is there a best practice approach?

Thanks,

Dharav