Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Performance Analytics Score does not Match Records Tab - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Performance Analytics Score does not Match Records Tab
KB0552914

Performance Analytics Score does not Match Records Tab


2178 Views Last updated : Jul 22, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

When you view a Performance Analytics detailed scorecard, the score displayed may be different than the number of records that appear in the Records tab. This is expected behavior for certain configurations.

Cause

This behavior may be caused by the following configurations:

  • When an indicator Aggregate value is a value other than Count, such as Sum
  • When you select an aggregate time series on the scorecard, such as 30d running AVG

In both of these configurations, the score displayed on the scorecard is the aggregate value. The Records tab displays the count of records, not the specified aggregate.

Additionally, the score may not match the Records tab even for a Count indicator:

  • When a before query business rule is defined for the table displayed in the Records tab. Business rules do not run during data collection, only when displaying the list of records.
  • A possible solution would be change the aggregate field for the indicator from Count to Count Distinct
  • Note: A Count, just performs a count and includes duplicates while a Count Distinct will ensure duplicates are not counted even if they are found for now and in the future within the database view or table. Once the field is changed to Count Distinct, a second dropdown will appear with the name Field.  This is the field that PA will use to make sure there are unique.  This field is typically set to Sys ID.

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.