web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Cannot edit Merge and Delete behavior in 1:N entity relationship

(0) ShareShare
ReportReport
Posted on by

Hi,

In 1:N relationship of Account entity, the delete and merge behaviors appear as 'Cascade All'.  Both option sets are read-only and I cannot modify it.

Please advise why is that and how can I modify these behaviors.

Thanks in advance,

Saima

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    ScottDurow Profile Picture
    21 on at

    This is most likely because your 1:N relationship is set to be 'Parental' in which case this behaviour is always used. You'll need to set the relationship to Configurable Cascading - you'll then be able to change these settings.

    hth

  • Suggested answer
    Community Member Profile Picture
    on at

    The Merge behavior never can be edited, it is a CRM restriction. This value is always "Cascade All" in the 1..N relationships from Account, Contact and Lead, that are the only entities that allow merging. In other entities the value is always "Cascade None".

    The Delete behavior can be edited. but not in every cases. In the case of Account this behavior can be edited only in 1..N custom relationships.

  • Community Member Profile Picture
    on at

    Entity: Account

    Relationship Type: 1:N

    The Type of behavior is currently set as 'Configurable Cascading'.  Below that, Merge and Delete option sets are in Read-Only mode.  The default value is appearing as 'Cascade All' for both delete and merge behaviors.

    How this behavior can be changed to 'Cascade None'?

  • Verified answer
    Community Member Profile Picture
    on at

    Hi again Saima:

    Here is a link about relationship types in CRM:

    msdn.microsoft.com/.../bb955307.aspx

    As you can read this behavior can't be edited:

    "Configurable Cascading Cascading rules can be configured for most actions. For system relationships, you can select the cascading rules for all actions except merge or delete. For custom relationships, cascading rules can be selected for all actions except merge. Cascading on merge is dependent on the referenced entity. If the referenced entity is an account, contact, or lead, the action cascades. Otherwise, it does not."

  • Community Member Profile Picture
    on at

    Hi Alvaro.  Thank you.  Now I can understand it better. We are planning to merge some accounts and have been concerned how this action will impact on cases, and contracts.  This link explains well.  Thanks again.

  • naconwa1 Profile Picture
    735 on at

    Is there a way to change this behavior through a plug-in or third party solution? This is seriously affecting our activity data.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
JS-09031509-0 Profile Picture

JS-09031509-0 3

#2
AS-17030037-0 Profile Picture

AS-17030037-0 2

#2
Mark Eckert Profile Picture

Mark Eckert 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans