TM1 Forum

Hi
Is there a setting in tm1 web (10.2.2) that will automatically recalculate a cube view once a value is entered to a cell? If I hit enter the cell remains green even if the views' AutoCalc option is switched on in the toolbar.
In the old web, hitting the enter resulted in data being recalculated and the arrow keys resulted in not-calculated just the cursor moving to the next cell.

Thanks

Hi,

If you want to have it 'recalc' for every entry, there is a setting in tm1web.cnfig file you need change. set RecalcOnDataValidationChange" value to 'True'

From the doc:

Specifies whether the default recalculation behavior will be overridden when changing the value of a data validation list.

I do not think this is relevant here, or have you tested and it works for my question as well?

Thanks

Hi,

I found this parameter in Performance Manager:
"Enable recalculation on enter"


Now I have a different issue: if you untick this box, it works only for N: elements, which means, if you enter a value to a C: element, the break back happens automatically, independently from this box. Any ideas how I can prevent auto-breakback on C: elements? What I want to achieve is that the user enters some values on C: level but it only recalculates/breaks back after hitting the Recalculate button.

Thanks!

mvaspal wrote:Hi,

I found this parameter in Performance Manager:
"Enable recalculation on enter"


Now I have a different issue: if you untick this box, it works only for N: elements, which means, if you enter a value to a C: element, the break back happens automatically, independently from this box. Any ideas how I can prevent auto-breakback on C: elements? What I want to achieve is that the user enters some values on C: level but it only recalculates/breaks back after hitting the Recalculate button.

Thanks!

I think you will find there is no way around this behaviour and if you think about it it makes sense that it works this way. If you spread on a consolidation there may be (most probably will be) children or other descendants of the consolidation in the view. So the spread has to be immediate, otherwise other you might overwrite other cells that might be either leaf or other consolidations with inconsistent numbers, and then if the spreads happened only on enter and there were conflicting inputs then which priority order should be applied to decide what the final value should be? The obvious way to solve this issue is to make the update of spreads immediate.

Hi
I agree with you in a certain extent, it makes sense what you say. But then why does CAFE allow this behavior? You type in values on C: level and they are spread once you hit Commit. It allows entering conflicting N: and C: values parallel.

In terms of entering conflicting C: and N: values ... well, it depends how much you trust your users...it seems CAFE believes your users are smart enough but the web does not