Pega Insights showing higher count than export results when using Associations

User Experience
, ,
1

Hi Team,

We have observed a discrepancy in Pega Insights when an Insight includes fields from the primary class as well as fields from an associated class.

Scenario

  • Insight is built using an association between two classes.
  • Columns from both the primary class and associated class are included in the Insight.
  • The count displayed in the Insight is higher than expected.
  • However, when we export the results to Excel, the exported record count appears to be correct.

Example

  • Insight displays: 1,250 records
  • Exported results contain: 1,200 records (expected count)

Observation

The issue seems to occur only when fields from the associated class are used. It looks like duplicate rows may be getting counted in the Insight due to the join/association, while the export process is returning the distinct records correctly.

Questions

  1. Has anyone experienced a similar difference between Insight counts and exported results?
  2. Are there any known limitations or settings in Insights related to associations and joins?
  3. Is the Insight count calculated before applying any distinct/grouping logic that might be applied during export?
  4. Are there specific configurations we should verify to ensure consistency between the displayed count and exported results?

Any guidance or known solutions would be greatly appreciated.

Thanks!

2

@Mohan_Rao_Alladi I have not seen this for Associations. I have seen this when you add fields from embedded data, but this is expected as the classes are joined.

The fact export gives you a different result to UI, suggests some sort of bug here. I would be raising a ticket with My Pega Support for investigation and a deeper look at your configuration.

Please share the ticket number or outcome, as I’m very interested to understand what is happening here!

3

INC-D47841 is raised for this, Below are the comments from Support team.

Root Cause:
This issue occurs due to post-processing logic in the Insights and Dashboards data pages when association columns are included in your view. The UI count includes both parent records and any duplicated records resulting from the association join, while the Excel export correctly shows only the actual unique records. This is a known product defect that has been identified and resolved in Pega Platform version 24.2.4 and higher.