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

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

• What are aggregates/aggregate tables and where is it used?

  When a KPI is published using a set of measures and dimensions, it dynamically refers a specific aggregate table and fetches results from it.

• 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

• Do all the aggregate tables specified in data model need to have a sequence number?

  All aggregate tables specified in the 'dbmodel.xml' have to be given a unique sequence number in order to apply the order of execution. And sequence is not just the running number for all tables; it has to be grouped by data mart. Please contact ARC ...