Getting Invalid KPI definition error while trying to access KPI.

• Related Articles

• Getting errors in Firefox while trying load data exceeding 3000 values. How to solve the issue?

  Firefox browser has a limitation to allow data exceeding 3000 values. If the external CSV file contains more than 3000 filter data then, script error will be displayed. Try loading data not exceeding 3000 values.

• Why does the KPI working fine in Administrator module produce an Invalid error in Analyst module?

  If the definition of the KPI has undergone some changes in the data model, KPI shows the 'Invalid' message. Either a measure or a dimension associated with the KPI might have undergone a change. Here is an example of such and issue and its solution. ...

• When drilled down from 'Quarter' to 'Month', KPI shows the error - 'java.lang.Exception: Query Execution Failed ! :Invalid column name #DATE_KEY#'. Why?

  It happens when the 'OrderByDes' column for MONTH and WEEK levels of TIME dimension is specified as 'OrderByDes="#DATE_KEY#", in the dbmodel.xml file. Modify that to 'OrderByDes="DATE_KEY". Note: This is advanced configuration and affect whole ...

• 'Sales Discount' KPI shows an exception as, 'Invalid KPI'. Why?

  The KPI's definition must have got altered. There will be an issue with the metadata related to the KPI like Measures/Dimensions. You can alternatively check for the KPI validity from Administrator --> KPI Management and verify ...

• The KPI doesnot execute when drilled-down from 'Quarter' to 'Month'. It throws the error - 'java.lang.Exception: Query Execution Failed! : Invalid column name '#DATE_KEY#' in the log. How can the issue be solved?

  If the 'orderByDes' column for MONTH and WEEK level in TIME Dimension in 'dbmodel.xml' file is specified as 'orderByDes="#DATE_KEY#" then, the KPI will fail. In such cases, ensure that the 'orderByDes' column of the individual levels are specified as ...