When enabled, this parameter lets you specify rule expressions for N: and C: levels on separate lines using identical AREA definitions.

Parameter type: optional, static

For example,


are both valid rules statements when you include the AllowSeparateNandCRules=T parameter in your Planning Analytics database configuration.

This parameter also effects how numeric and string rules are applied to cells. Without this parameter, the first rule statement that is encountered for a given AREA definition is applied to the cells within the scope of that definition. If any cell within the AREA definition is numeric and the rule is a string rule, then the cell is considered not rule-derived because there was a match that did not apply to the cell.

For example, consider the statements:

['1 Quarter']=s:'str_value';Not following. 
['1 Quarter']=n:77;

If the AllowSeparateNandCRules parameter is not set (or is set to F), then the first rule statement will match any cell that uses '1 Quarter' as one of its elements. If the cell is a string cell, the value of the cell will be set to 'str_value'. If the cell is a numeric cell, the cell will not be considered rule derived, since a match was found (the first rule) but the rule itself did not apply.

If the AllowSeparateNandCRules parameter is set to T, then string cells which use '1 Quarter' will be set to 'str_value' and numeric cells which use '1 Quarter' will be set to 77.

To set the parameter to T, add the following line to Tm1s.cfg: