KPI shows error when drilled down from one level to another. Why?
It can be due to the incorrect data type of the measures used in the KPI. This needs to be verified at the metadata management module.
Related Articles
KPI produces an error when drilled down from one level to another. What could be the reason?
Most often, drilling down from one level to another level poses problems due to incorrect data type of the measures used in the KPI. Check for the data type of the measures and correct them accordingly in the 'dbmodel.xml' file.
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 ...
The graph in dashboard portlet shows the error "arc.records.more.apply.filters" when drilled down. Why?
This issue can occur if the filters for the graph are configured with more filter values. To resolve the problem, provide lesser filter values. When the filters for the graph are configured with more values, the rows returned exceeds the capacity of ...
KPI log shows the error 'java.lang.Exception: Query Execution Failed ! :Ambiguous column name'. Why?
KPI query returns ambiguos column error, when a particular measure is present in both the Aggregate table (Example, AGG_WLY_STR_DEPT_Details) and DIM table (example, DIM_STORE). You have to change the column name in any one of the table, for the KPI ...
Can I create an expression measure using another one?
No, you cannot. You can use only base measures within an expression measure.