SYMPTOM:
A report returns repeated values across the same attribute element even when the data in the warehouse is different.

The report shown above generates incorrect values for Metric 2. The SQL generated is the following:
select a11.Category_ID Category_ID,
a12.Category_Name Category_Name,
a11.Fact1 WJXBFS1,
a11.Fact2 WJXBFS2
from FactTable a11
join Category a12
on (a11.Category_ID = a12.Category_ID)
When executed using ODBC test tool or a native tool the results come back correctly. The values across the Category for Metric 2 are not repeated in the database

CAUSE:
This is working as designed. The Strategy object definitions are not consistent with the structure in the database tables. The report is hitting the lowest level of aggregation detected by Strategy on the fact table. This can be checked by looking at the fact table used to calculate the metrics. The table will list the attribute used in the report as a unique key in its definition:

The effect is that Strategy assumes that one single row will be present per Category as it is the only attribute marked as the unique key.
ACTION:


Both actions described above will generate a report that performs aggregation as shown below:
