ForceReevaluationOfFeedersForFedCellsOnDataChange
- macsir
- MVP
- Posts: 785
- Joined: Wed May 30, 2012 6:50 am
- OLAP Product: TM1
- Version: PAL 2.0.9
- Excel Version: Office 365
- Contact:
ForceReevaluationOfFeedersForFedCellsOnDataChange
Just a thought, if this parameter is not set, is there any possibility that you got wrong result because the conditional feeders are not re-evaluated automatically? If yes, how to prevent it?
-
- MVP
- Posts: 2836
- Joined: Tue Feb 16, 2010 2:39 pm
- OLAP Product: TM1, Palo
- Version: Beginning of time thru 10.2
- Excel Version: 2003-2007-2010-2013
- Location: Atlanta, GA
- Contact:
Re: ForceReevaluationOfFeedersForFedCellsOnDataChange
1) Set the parameter to true.macsir wrote:Just a thought, if this parameter is not set, is there any possibility that you got wrong result because the conditional feeders are not re-evaluated automatically? If yes, how to prevent it?
2) Don't use conditional feeders.
3) Run a TI process that reprocesses feeders every time a user changes data in a cell that uses a conditional feeder to feed another cell.
- macsir
- MVP
- Posts: 785
- Joined: Wed May 30, 2012 6:50 am
- OLAP Product: TM1
- Version: PAL 2.0.9
- Excel Version: Office 365
- Contact:
Re: ForceReevaluationOfFeedersForFedCellsOnDataChange
Thanks, tomok for the quick reply. So it is possible that user changed the value and the new location is not fired?
For the #2, Do you mean that using slightly overfeeding instead?
For the #2, Do you mean that using slightly overfeeding instead?
- macsir
- MVP
- Posts: 785
- Joined: Wed May 30, 2012 6:50 am
- OLAP Product: TM1
- Version: PAL 2.0.9
- Excel Version: Office 365
- Contact:
Re: ForceReevaluationOfFeedersForFedCellsOnDataChange
The reason I am asking is that, I found my reloading actual process is really slow because most data is different from what have been loaded last time. And if I turned this parameter off, the reloading time is back to normal. And because my model requires lots of user data change and there are lots of conditional feeders, I would prefer to turn this parameter on at default.
Apart from the three options you provided, I am thinking to have an external little program to automatically change this parameter on and off. Lets say, first turn it off for reloading actual and then shut down the server change the parameter to TRUE and restart the server for daily operation. Is that reasonable? Any advice is welcomed.
Apart from the three options you provided, I am thinking to have an external little program to automatically change this parameter on and off. Lets say, first turn it off for reloading actual and then shut down the server change the parameter to TRUE and restart the server for daily operation. Is that reasonable? Any advice is welcomed.
-
- MVP
- Posts: 2836
- Joined: Tue Feb 16, 2010 2:39 pm
- OLAP Product: TM1, Palo
- Version: Beginning of time thru 10.2
- Excel Version: 2003-2007-2010-2013
- Location: Atlanta, GA
- Contact:
Re: ForceReevaluationOfFeedersForFedCellsOnDataChange
Yes, that's entirely possible if you have some IF conditional logic in your feeders. That's the whole purpose for that parameter.macsir wrote:Thanks, tomok for the quick reply. So it is possible that user changed the value and the new location is not fired?
I'm simply saying that if you have conditional feeders AND they're causing you an issue because you refuse to use the ForceReevaluationOfFeedersForFedCellsOnDataChange parameter then one option is take out the "condition" in your feeders. Whether results in overfeeding I have no clue based on the information given. Probably so, otherwise why you put a condition in there?macsir wrote:For the #2, Do you mean that using slightly overfeeding instead?
- macsir
- MVP
- Posts: 785
- Joined: Wed May 30, 2012 6:50 am
- OLAP Product: TM1
- Version: PAL 2.0.9
- Excel Version: Office 365
- Contact:
Re: ForceReevaluationOfFeedersForFedCellsOnDataChange
Thanks, so far no issue except the one I described above. I think rather than only turning in this parameter, I should focus on how to resolve it fundamentally. If the new location is not fired, then it must be some situations I haven't considered before. I should adjust conditional feeders accordingly.