SUMMARY:
This technical note describes an issue when adding a custom subtotal with a subset of attribute elements to a report or a grid in a report services document. If the custom subtotal is created with a Fact instead of a metric in the case statement, the subtotal does not display on the grid and will generate a ‘type mismatch’ error when editing the custom subtotal.
SYMPTOM:
In Strategy 9.x, users can create custom subtotals with a subset of attribute elements in the calculation. However, when adding this custom subtotal to a report or a grid in a report services document, the custom subtotal does not display, like shown below:

When the user edits the custom subtotal, the report or document appears in the list of objects dependent on the subtotal. If the user attempts to remove the report or document object, an error appears and does not allow the user to save the changes, as shown below:

Type mismatch
Sum(Case((Year@ID = 2011), Profit, (Year@ID = 2012), Profit, 0)) {~}

CAUSE:
This issue occurs when the case statement in the custom subtotal’s definition references a Fact instead of the metric.
ACTION:
Replace the Fact in the case statement with the corresponding metric.
For more information on creating a custom subtotal, refer to technical note KB47180 : How to create a custom subtotal that includes a user-defined subset of available attribute elements in its calculation in Strategy 9.x.