Unable to Merge Records for Unknown Reason

(0) Share

Report

Posted on by Community Member

Hello,

I have been having a small issue with our CRM system for a while now. A user is trying to merge two records together. However, every time he does, is receives a popup that just says "Business Process Error: The entity cannot be updated because it is read-only". However, neither of the records in question are read-only, and the user has all permissions for both entities.

So, I am unsure what could be causing this issue. Does anyone have any idea what it might be?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Piyush Paliwal 817 on at

Like (0)

Report

Looks like there is a workflow or a plugin that is not allowing the update to go through. Can you confirm if there are any plugins/workflows running on this entity?

Was this reply helpful? Yes No
Suggested answer

Dynamics365 Rocker 7,755 on at

Like (0)

Report

When you merge records then it's all associated record will be assigned to primary record.

Please make sure that all records are active.

Was this reply helpful? Yes No
Suggested answer

gdas 50,091 Moderator on at

Like (0)

Report

Hi Philip ,

Did you tried with System Administrator role?If no then please try once?

What are the entities are you trying to merge ?

Some system entities cannot be updated when closed - like quote, contract & invoice etc. So you have to check that also.

In addition please check below old thread-

community.dynamics.com/.../245631

Was this reply helpful? Yes No
Suggested answer

RaviKashyap 55,410 Moderator on at

Like (0)

Report

Hi,

When you merge a record, all the related records Activities, Contacts etc also reparent from subordinate to master record. Now, if the related record is already readonly then it will fail to reparent and will through you the entity cannot be updated error message.

Check all the related records of the account you are merging and see if there are any readonly records. Most of the time, it is the related case records which causes this issue.

Hope this helps.

Was this reply helpful? Yes No