TM1 Forum

I've come across "Evaluation Stack Overflow" fired by feeders. However, we are encountering the same error generated by the use of the "CellsUpdateable" function in TI. I am running a process that has a single line checking the updateability of a single cell (for debuging purposes). The process aborts with the above error message in the log.

This cannot (I assume) be caused by feeders - so it must be caused by something else. Presumably it is related to the number of steps the app has to go through to determine the updateability. There are 5,000 odd lines of rules/feeders with a lot of conditional formulae as well as liberal use of "Continue". Is it possible that TM1 is finding it too complicated to evaluate the cell status? Has anyone else come across this?

We are using version 9.1.3

thanks ....................hugh

I've seen the Evaluation Stack Overflow pop up when you have a circular reference.

Are you able to pull the cell in a cube view that you're referencing in the CellISUpdateable function? I bet when you try and pull that cell, it throws the same error in the log file...

I'm not sure but it's possible that the cellisupdateable function works by putting a value in a cell, then resetting it back. If that is indeed how it works then yes, this will kick off some feeders as inputting a value will fire feeders.

The error you mention has in my experience been invariably due to do a long running feeder chain. For example if you have an opening balance, movement and closing balance, and you want to feed the closing balance from each period into the succeeding period's opening balance, then you get potentially a very long chain of feeders.

The only real work around for this is breaking the feeder chain at one point in time and using TI to populate that cell, and set another chain of feeders in motion from there.

HTH,
Martin