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

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

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

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

  The foreign key must be missing for the to the specified aggregate table / view in the data model (db_model.xml) file. Add the requisite 'FOREIGN_KEY' for the required dimensions.

• SQL View is not working properly for computed measures. Why?

  Computed measures are not displayed in the query as they are calculated run time by the Application itself.