Title:

Enhancement Request: Identify Related Entity Causing Duplicate Key Conflict During Lead Merge

Product

Dynamics 365 Sales / Dataverse

Scenario/Problem Statement:

When merging Lead records in Dynamics 365 Sales, users may encounter the error:

“Duplicate record. A record with these values already exists.”

This error occurs during the merge operation when Dataverse attempts to reassign related (child) records from the subordinate lead to the master lead, and one or more related records violate a unique constraint / alternate key.

Currently, the platform does not provide any indication of:

• Which related entity
• Which relationship
• Or which specific record

is causing the duplicate key conflict during the merge process.

As a result, users must manually disassociate related records one by one to identify the conflicting relationship, which is time‑consuming and error‑prone—especially in environments with many custom entities and relationships.

Current Behavior

• Lead merge fails with a generic duplicate record error.
• No details are provided about:
• The related entity
• The relationship name
• The specific record or alternate key involved
• Users must manually inspect and disassociate related records to proceed.
• Once conflicting related records are disassociated, the merge completes successfully.
• This behavior is currently by design / expected.

Expected Behavior:

Provide actionable diagnostics when a merge fails due to duplicate key conflicts by:

• Identifying the related entity and relationship causing the conflict
• Optionally surfacing:
• The alternate key / unique constraint involved
• The record ID(s) causing the conflict
• Returning a clear and descriptive error message, for example:

“Merge failed due to duplicate key conflict on related entity via relationship .”

This would allow users and administrators to immediately address the issue without manual trial‑and‑error.

Business Impact

• Significant time spent troubleshooting merge failures
• High operational overhead in environments with complex data models
• Reduced productivity for sales and data management teams
• Increased support cases for an otherwise predictable platform behavior

Value/Benefit

• Improves user experience and transparency
• Reduces support and operational effort
• Helps administrators proactively resolve data integrity issues
• Enables safer and faster data consolidation during lead management

ASK:

Requesting the Product Group to consider enhancing the Lead Merge operation to surface detailed information about the exact relationship or entity causing duplicate key conflicts during merge.