When defining a new aggregate table, there is no option to select 'Foreign Key'. What could be the reason?

• Related Articles

• 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

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

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

• Unable to select certain store codes from Store filter. What could be the reason?

  This might be due to the duplicate store codes present in DIM_STORE. For e.g., Store code = 13. It contains two store codes (13) as active (i.e., column->active=1). Among the two, one is an old store(column->latest=0) and the other is the latest ...

• 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