This issue is illustrated here:
#447
It is most noticeable when the column is Mapped (Pricing Type, for example), which makes query behavior inconsistent with the Reporting Request.
Given a Dimension located in the fact with multiple expected useful output values, this dimension gets collapsed as it is not the most granular key alias on the table.
This issue is illustrated here:
#447
It is most noticeable when the column is Mapped (Pricing Type, for example), which makes query behavior inconsistent with the Reporting Request.
Given a Dimension located in the fact with multiple expected useful output values, this dimension gets collapsed as it is not the most granular key alias on the table.