Microsoft Dynamics 365 | Integration, Dataverse...

Risks with Merging records

(2) Share

Report

Posted on by ML-24050027-0

Hi, we have identified a number of duplicate vendor and customer records.

Has anyone identified any issues or risk in merging records in MS Dynamics 365?

Categories:

Dynamics 365 general

All responses (2)

Answers (0)

Suggested answer

Mansi Soni 4,400 on at

Like (2)

Report

Risks with Merging records

Hello, merging duplicate Customer or Vendor records in Business Central is generally safe when done carefully using the built-in Merge Duplicate function, but there are some important considerations and risks:

Linked Data Risk: If the duplicate records have different posting groups, payment terms, or dimensions, this may create inconsistencies in reports.

Open Transactions: Any open documents (e.g., open orders, quotes) should be reviewed before merging to ensure they’re transferred appropriately.

Permissions: Ensure only authorized users perform merges, as it's irreversible once completed.

Customizations & Extensions: If your environment includes custom fields, workflows, or integrations, test the merge process in a sandbox first to ensure these don't break or lead to data corruption.

Best Practice: Always back up your data or test the merge in a sandbox environment before performing it in production. Also, review and clean master data fields to standardize values post-merge.

Hope this answer will help you!

Regards,
Mansi Soni
Suggested answer

Anupam.khasia 12 on at

Like (0)

Report
Risks with Merging records

Hello @ML-24050027-0,

This is more generic question. Risk involved in merging records would vary upon implementation or customization done or records. Merging records in background change all association

Change data from primary source to target source

Change all association of primary source records including related records.

Inactive primary records

In my perspective , following areas you need to look before doing

Data & Security

Integration if implemented