The aggregate table is defined properly in the 'dbmodel.xml' but KPI refers to an incorrect one. Why?

• Related Articles

• 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

• The parameter used in an aggregate table that refers a view sql does not work. What could be the reason?

  Parameter defined in the "view SQL" query should not be enclosed with single quotes. Attached screen print can be referred

• One of the column names in the KPI grid is incorrect? It is not the column Name being displayed?

  One of the possible scenarios: ------------------------------------------ All the measures must be mapped to the same db column. The measures are picked up based upon the first created measure ID.

• 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.