SYMPTOM:
When running a Report Services Document in Strategy 10.x, changing the evaluation order of a derived metric from "Default" to "1" makes allows for the calculation to come after a derived element.
By default the Analytical Engine will calculate derived metrics before derived elements. However, if the evaluation order of the derived metric is set to "1" then the derived metric will calculate after derived elements. Note that derived elements will never appear in the evaluation order editor in a Report Services document because the derived elements must be calculated at the attribute level. They will therefore be calculated in the virtual dataset of the document and will not be subject to evaluation order settings under Grid Data Options.
CAUSE:
This behavior is by design. "Default" is always evaluated before non-default evaluation orderings.
Because derived elements are calculated in the virtual dataset of a Report Services Document they are not subject to evaluation order settings under Grid Data Options. Thus it is impossible to change the evaluation order of a derived element to a non-default setting. Therefore, changing the evaluation order of a derived metric to any non default-setting will cause it to calculate after any derived elements.
ACTION:
To ensure that a derived metric is calculated before any derived elements, the derived metric's evaluation order must be set as "Default." Any non-default setting will cause the derived metric to be calculated after derived elements.
