The KPI displays an error - "For input String 'COR'" while analyzing it from one of the views among three views. However the KPI produces results with the other two views

• Related Articles

• The KPI displays an error - "For input String 'COR'" while analyzing it from one of the views among three views. However the KPI produces results with the other two views. What could be the problem?

  Possible reasons for the KPI to display the exception as stated is, there would have been a mismatch between the data type of the measure that is defined and the data type of the column to which it is pointing to in the data model (dbmodel.xml) file.

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

• Why is the graph linked to the KPI not producing results when drilled-down? However the KPI produces results when drilled-down.

  By efault, the graph linked to the KPI is pinned. In such cases, we have to set the Default Pin Graph' Option available in Visual Personalization to Do not pin graph . Pin Graph is a graph utility which allows you to freeze a graph at its current ...

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

• KPI Preview produces results but does not work when analyzed. Why?

  One of the reasons could be: The KPI might have been published using a Force aggregate option (opting for the aggregate table which the KPI has to refer to). The pre-requisite is all the measures used in the KPI must be available in the aggregate ...