Users may notice duplicate entries for the same Related Party when exporting data or running reports, even though the Related Party appears unique within the UI. This typically happens when multiple active associations reference the same Related Party entity, or when historical relationships were not properly deactivated during ETL merge processes. In some cases, duplicates can also result from reporting queries that join on non-unique fields such as entityName instead of unique identifiers like entityId or alternateId.
Solved
Why do duplicate Related Party records appear in my data exports or reports, even though each Related Party should only exist once?
Best answer by jawadkhan
Duplicate Related Party entries usually occur when multiple active associations point to the same Related Party entity, or historical associations were not properly deactivated during ETL merges.
Common causes
- Two or more verified relationships reference the same Related Party ID.
- ETL updates created overlapping association records instead of replacing them.
- Reporting logic joins on non-unique fields (like entityName) instead of unique identifiers (entityId or alternateId).
To clean up:
- Deactivate (not delete) outdated associations — this maintains audit history.
- Update ETL jobs to set isActive = false on superseded relationships.
- In reports or exports, always join using entity IDs, not display names.
Recommendation: Use the Fenergo Reporting Data Store (RDS) for nightly deduplication audits - it can detect multiple active links to the same Related Party and flag inconsistencies for review.
Duplicate Related Party entries usually occur when multiple active associations point to the same Related Party entity, or historical associations were not properly deactivated during ETL merges.
Common causes
- Two or more verified relationships reference the same Related Party ID.
- ETL updates created overlapping association records instead of replacing them.
- Reporting logic joins on non-unique fields (like entityName) instead of unique identifiers (entityId or alternateId).
To clean up:
- Deactivate (not delete) outdated associations — this maintains audit history.
- Update ETL jobs to set isActive = false on superseded relationships.
- In reports or exports, always join using entity IDs, not display names.
Recommendation: Use the Fenergo Reporting Data Store (RDS) for nightly deduplication audits - it can detect multiple active links to the same Related Party and flag inconsistencies for review.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.