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

• Related Articles

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

  If there are a large number of pre-selected values which are saved as part of filter, the KPI might not respond at times as it has to pre-load and read the object containing such large number of filter values. You could select these filter values ...

• In the KPI Grid Utility - SQL View, does the computed measures show as "SQL Generated from KPI"?

  They are computed measures and will not be displayed in the query as it is calculated by the application itself.

• Why do I get the error "For Input String 'COR'" while analyzing KPI data from one among the three views? I get KPI data results properly with the other two views.

  The reason could be a mismatch between the data types of the measure defined and the column to which it is pointing to, in the data model.

• 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 report is not displayed properly for the KPI, although Query executes. How can it be corrected?

  In case there are large number of values to be displayed in the KPI grid then, the grid loads the data part by part instead of loading the entire data set at once. This can be defined using the following arc.properties: arc.datagrid.partly.size = ...