Current Behavior
When merging duplicate records in Dynamics 365 Sales, the subordinate record is not deleted—it is set to inactive. Users must then manually locate and delete the inactive record if full cleanup is required.
Issue
This approach introduces several challenges:
- Unnecessary data growth – Inactive duplicate records accumulate over time, contributing to data bloat and reduced reporting clarity
- Inefficient process – Merging requires an additional manual step to fully remove duplicates
- Inconsistent data hygiene – Inactive records are often left behind, leading to confusion and potential downstream impact
- Duplicate detection limitations – Not all duplicates can be prevented (e.g., legal name vs nickname such as “Blanche” vs. “Bunny”), making efficient cleanup essential
Suggested Enhancement
Provide an option to:
- Automatically delete the subordinate record during merge, or
- Allow configuration between:
- Deactivate (current behavior)
- Delete (new option)
Business Value
- Improves data quality and system cleanliness
- Reduces administrative effort for high-volume environments
- Prevents accumulation of unnecessary inactive records
- Aligns merge functionality with common user expectations and legacy CRM capabilities
Comments
In real-world use, duplicate detection cannot account for scenarios like nicknames vs. legal names (e.g., “Blanche” vs. “Bunny”), so duplicates still occur. If Blance Moses is in our system and she interacts online using her nickname of Bunny Moses duplicate detection can't compare "Bunny" to the nickname field already in the system under Blance's record. Someone who doesn't know her will inadvertantly create a new record for her.This makes it especially important that the merge process fully resolves duplicates in a single step rather than leaving inactive records behind.
Category: Account, Contact, Calendar and Activity Management