Details of SQL filters in DTP operations

Dimensional attributed in SQL filters

It is possible to refer to CCH Tagetik dimensions in the execution conditions and SQL filters in DTP activities and operations. The references must be defined with the syntax of the cell fields used in the reporting.

Example: the syntax for checking for the presence of entity EN_00, as a condition for the execution of an activity, is as follows: ${$Entity.code} = 'EN_00'. If the outcome is positive, the result is 'EN_00' = 'EN_00' and the activity is run.

The syntax for checking, as an execution condition, for the presence of an entity EN_00 in a node, is 'EN_00' in (${$Entity.code}).

The system checks that entity EN_00 is among those present in the activity run node.

The cell field is replaced with the value resulting from the checking of the condition reported in inverted commas. If the outcome of the check is a set of values, the cell field is replaced by the set of values in inverted commas separated by commas.

The syntax ${@PARAMETRO} can be used, in the cell field, to refer to the parameters present in the form parameters definition (see ).

Note: the outcome of the DATASETPARTITION cell field check is not reported in quotes as it is a table name.

Syntax supported in SQL fields

In fields that support SQL language the DTP allows the following syntax, converted in the run step.

Element	Description
System parameters	- See System parameters.
@PARAMETRO@	Parameters defined at the workspace level, which take on the value indicated in the default formula present in the definition of the same parameter.
${@PARAMETRO}	Global parameters defined in forms, supported by SQL scripts defined at the Activity, Operation, Matching fields and Special methods level.
Unified SQL syntax	See Unified SQL syntax.