The KPI hangs while analyzing. What could be the reason?

• Related Articles

• Analyzing scheduled KPI affecting CPU usage and performance. What could be the reason

  For Scheduled KPI, when we click on 'Analyze' button, a 'Schedule Report' page gets displayed. There's an option to select the generation type of the output (either Excel or XML). By opting for 'XML' method, the data retrieval will be considerably ...

• The KPI grid hangs, or shows the data loading bar 'in progress' even after complete data is loaded. Why?

  Verify the following property values in 'arc.properties' file. For better performance of grid, max_row_count = 500 arc.datagrid.partly.size = 1000 arc.distributed.parsing.size = 20

• The query generated while analyzing the KPI is not proper. Why?

  One of the reasons: If two measures are having a same name, then there will be mismatch while constructing the query and the data fetched will be incorrect. Ensure unique names are provided to measures.

• Store filter selction shows 50 records but after analyzing the KPI, the report generates only 36 records

  The KPI usually shows up only active stores and the missing stores might be inactive stores. Hence, these donot show up while analyzing the KPI. The KPI query can be cross-verified by executing the query in the db

• If we add a new view while analyzing a KPI, it is retained even after logging off.

  The new dimension added as a view is expected to retain permanently irrespective of whether you are within the session or not. Any user possessing KPI utilities as part of his/her security will be allowed to add new dimensions as view