Merging accounts and contacts are the most common functionality in Dynamics CRM/365, used to merge duplicate records. Users cannot merge records without proper security permissions. Merging should be allowed as shown in the screenshot below. It is available in the Business Management tab.
Still, just by granting the Merge permission, the user won’t be able to merge the records as there would be little other permission missing which is quite unrelated to the merge operation.
The user gets the following error:
Insufficient permissions to merge Accounts
The following permissions need to be taken into account:
- 1. Whenever the user merges the records, the application also checks that the user has permission to read and write on both records, which he is merging. If the required permissions are not on any record, it will not be able to merge.
To understand this, consider there are 2 Business Units (A and B) in D365 and both account records belong to different business units. Now, if that user who will be merging these 2 records belongs to a Business unit A and he has Read permission on Account entity at Organization Level but at the same time, he should have the Write permission only at Business Unit level, the user won’t be able to merge.
- 2. Apart from the Read/Write permissions, “Share” permission should also be granted on the Organization level.
3. The most bizarre permission granted to a user is to read on an opportunity-related entity at the organization level. When merging without this permission, the user gets an error that doesn’t give any clue about the required permissions.
Allowing to merge alone, the user will not be able to merge. It will also need proper permission to write, share and offer on the main entity (account/contact). We are the best Microsoft Dynamics CRM Consultant Company and our team would love to share such a guide, so follow us here to learn more.