Why is the KPI not referring the correct aggregate table that is expected to refer?

• Related Articles

• Which aggregate table will the KPI refer to fetch results when there are multiple aggregate tables?

  For the combination of measures and filters chosen in the KPI, if there are multiple aggregate tables then, you can define sequence for tables in the data model For Example, 1. 2. 5. 6.

• KPI not referring correct table to fetch results. What could be the reason?

  Possible reason: ------------------------ The KPI must be referring to the tables (aggregate table / views) which is specified at the time of publishing the KPI (using 'Force Aggregate' option). The KPIs must always refer to the particular table ...

• The KPI refers to the incorrect aggregate table although the correct aggregate table that is to be referred is defined in the 'dbmodel.xml'

  If the aggregate sequence of two different aggregate tables is either same or defined incorrectly then, the KPI refers to an incorrect aggregate table. Hence, ensure that the aggregate sequence is unique and properly defined

• Why is the KPI not showing Daily data and always referring to Monthly aggreate table?

  If the KPI is a cross tab KPI, the KPI must be configured in such a way that the 'Month' is used in the cross tab. Therefore, it always refers Monthly level aggregate table irrespective of the filters you select in the KPI. In short, in order to view ...

• After Publishing the KPI with Calendar(Business/Gregorian) its not referring the correct Aggregates. How to fix this?

  This issue occurs if the Graph linked to the KPI does not have calendar filter. So even if the KPI with Calendar Filter hits to proper respective Calendar Aggregate Table, after analyzing KPI, its hits the Standard Aggregate Table. To fix this issue, ...