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 specified as per the sequence defined in the data model.
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.
Why is the KPI not referring the correct aggregate table that is expected to refer?
This problem can occur if the force aggregate is chosen as part of the KPI definition during publishing. So each time, the KPI is analyzed, it refers the particular aggregate table.
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, ...
Why is the Markdown Analysis KPI not hitting the correct table?
This problem can occur if the force aggregate is mentioned for the KPI definition of Markdown Analysis. So each time, the KPI is analyzed, it hits AGG_WLY_STR_DCS aggregate table. To resolve the issue, please check and modify the aggregate table to ...