Why is the Markdown Analysis KPI not hitting the correct table?

• Related Articles

• 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 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 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 Weekday analysis by branch KPI not working properly?

  For the Measure C170 the DB_COLUMN_NAME (date_key) was mentioned in lower case. whereas in DB the column name (DATE_KEY) is upper case. Change the Measure "C170" DB_COLUMN_NAME to upper case, the KPI should work fine.

• Why the KPI section not displayed back for analysis, after I select all branches?

  This problem can occur due to presence of special characters present in one of the branch descriptions. Do not use special characters so that the problem can be avoided.