Overrides

In some cases it is necessary to define a TGKML script where the output account has a specific value on a given dimension. This requires the concept of override which allows to specify a fixed value (also NULL) to assign to a given dimension. In this way the system firstly deletes data on the database filtering by this overridden value and then saves data setting the dimension where the override has been defined with the fixed value specified in the output part of the script.

The scenario and the period are the only dimensions where an override cannot be defined.

Tagetik allows to

override a dimension's value. [LO].[X00000](Dest2.[D11]) :=...

In this case the system writes the script's result on gross data of the account X00000 and of the element D11 of the custom dimension 2;

Override a dimension's value to null. [LO].[X00000](Dest2.Null) :=...

In this case the system writes the result of the script on gross data of the account X00000 and of the element of the custom dimension 2;

override the value on a hierarchy's node. [LO].[X00000](Dest2.[01|$]) :=...

In this case the system writes the script's result on gross data of the account X00000 and on all the elements of the custom dimension 2 which are related to the overridden node, namely the node $ of the hierarchy whose code is 01;

override the same element defined in the input filters. [LO].[X00000](Entity.ForceOnFilter) :=...
define an override using the Ancestor and Parent utilities.
[LO].[X00000](Dest2.Parent([01]) :=...

In this case the system, after calculating the input element by element, sums up the results of the elements related to the same parent node in the hierarchy 01 and writes the result on the reference element defined for such node

[LO].[X00000](Dest2.Ancestor([01],3) :=...

In this case the system, after calculating the input element by element, sums up the results of the elements related to the same parent node of level 3 in the hierarchy 01 and writes the result on the reference element defined for such node.