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

• Related Articles

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

  The aggregate sequence of these two tables may be the same or defined incorrectly. Ensure that the aggregate tables are unique and defined properly.

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

• 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

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

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