Hi Justin,

What you are seeing is the symptom of individual member values and Totals being retrieved from the database as individual entities. When you hide some of the individual members in the client, the database Total "does not know" about this, and will still show the original total.

You should add your own calculated Total to your crosstab. You may try with the predefined Total calculation from the Calculations tab. In more recent versions it should automatically pick up only the visible members. If you are still seeing a problem, you may try with a Custom calculation, as a new row, like this:

sum(0, all(v), 0)

BR / Ole

All right. Same problem. Different solution.

The problem is still due to totals and subtotals being retrieved from the database and the database not knowing that you have hidden something in the client.

The solution I propose here is for a two-level hierarchy:

1. Keep the Total calculated row you did previously.
2. Add a new, custom calculation, as a calculated column:


3. Optional: Go into your calculated Total, "Calculate in intersection", to include the new calculated column in the Total calculation.

Calc explanation: If you are at a node without children, then simply transfer the value, otherwise if you are at a node with children (the subtotal nodes) then sum up all the visible children.

The solution complexity will increase if you have deeper hierarchies or if you have dimensions on the horizontal axis of your crosstab. Let me know if that is the case.

BR / Ole