Enable Javascript

Please enable Javascript to view website properly

Toll Free 1800 889 7020

Looking for an Expert Development Team? Take two weeks Trial! Try Now

Few Required Permissions to Merge Contacts and Account

Merging accounts and contacts is the most common functionality in the D365, used to merge duplicate records. A user cannot merge the records without having the correct security permissions granted. Merge permission should be given as depicted in the below screenshot. It is available in the Business Management tab.

Required Permissions to Merge Contacts and Account

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.

User gets the following error:

Insufficient permissions to merge Accounts

Solution Approach

We need make sure the following permissions are considered:

  • 1. Whenever a user merges the records, the application also checks, that the user has Read and Write permissions on both the records that he is merging. If required permissions are not on any of the records, he won’t 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 as well.
  • 3. Most bizarre permission to be given to the user is Read permission on the Opportunity Relationship entity at the Organization level. When merging without this permission, the user gets an error that doesn’t give any clue for the required permissions.
    Required Permissions to Merge Contacts and Account

Conclusion:

Allowing merging alone, the user will not be able to merge. It will also need proper permission to write, share and opportunity on the main entity (account/contact). We are the best Microsoft Dynamics CRM Consultants Company and our team would love to share such a guide, so follow us here to learn more.

You may like to read on Microsoft Dynamics 365 CE – Case Deflection in Customer Service Portals with Example

Recent Blogs

Categories

NSS Note

Some of our clients

team