Make calculated measures works with auto-generated members in cross tables

When using a calculated measure coming from a Dynamic Cube as sub-column of an auto-generated member (E.g. "Year to date Change") in a cross-table, the output results are calculated wrongly.

For "not calculated" measures, the output calculated in the sub-columns of "Year to date Change" consist of the gap between the current year value and the prior year value. However, the calculated measures still use their calculations instead of having the gap between the current year value and the prior year value calculated.

Real-life scenario

For exemple (see attached illustration), if we have an amount sold of $10 this year and of $8 the previous year, a margin of $6 this year and of $4 the previous year, we'll get under "Year to date Change" $2 ($10 - $8) for amount sold and $2 ($6 - $4) for margin. Those are the expected results.

However, for the calculated measure "margin %" which is calculated from "Amount Sold"/"Margin", we have 60% this year and 50% the previous year, but the cross-table will output 100% ($2 / $2) under "Year to date Change" instead of outputting the desired 10% (60% - 50%).

Current workaround

To get the expected result (the green cell in the attached file), we have to use tuples to recreate the calculation manually in the report query.

Proposed solution

We suggest to improve Cognos 11 compatibility with the Dynamic Cubes so that Cognos knows wich calculation to do when using a combination of a calculated measure and an auto-generated member.

Benefits of this idea

First, having Cognos using the calculated measures and auto-generated members well together is something expected by all users and when they find out about this issue, their trust in Cognos decline. Moreover, some users may take time to realise this issue and then use false information to make decisions.

Second, using tuples to fix this problem make the reports more complex, harder to maintain and require the users to understand how to use tuples, which is not the case for all of them. The ease of use of Cognos would then increase if this issue get fixed.

There is around 10 users affected by this problem at one of our clients. They heavily use their Dynamic Cubes, but I don't know how often they encounter this issue.

Thank you,