Cascade Relationship Behavior in Microsoft Dynamics CRM

31 Mar


This Blog is all about out-of-the-box Cascade Relationship Behavior and how to use it in more efficient way as per the business.

Default Behavior:

When an Account record “Company1, Inc.” is reassigned to another owner “User2” from “User1” then as per the default “Parental Relationship Behavior” all the completed and open child records i.e. Contacts, Opportunities, cases, Tasks, Emails, Phones calls, etc. are also reassigned to the another owner “User2“, but the important point here is to keep the completed Entities and Activities records impaired in any way to avoid confusions in future.


Is there a workaround for this?

Yes, to change this setting, here are few simple steps:

  1. Go to “CRM >> Settings >> Customization >> Customize the System >> Account >> 1: N Relationships”.


  2. Open the desire relationship record and change the “Type of Behavior” from “Parental” to “Configurable Cascading“.


  3. Now often we think of the meaning of these behaviors i.e. Cascade Active/Cascade User-Owned/Cascade None.
    • Cascade Active: means owner will change only if record is Active.
    • Cascade User-Owned: means owner will change only if the related record owner is same as Parent record.
    • Cascade None: means owner will not change.
  4. So, as I explained above, to avoid confusion in future about the completed records we just need to change the “Assign” field value from “Cascade Relationship Behavior” to “Cascade Active“.


By Abhisek Sriramka
Senior Software Engineer @Team DynamicsCRM.
Mindfire Solutions


Tags: , , , , , , , , , , , , , , , , , , , , , , , ,

One response to “Cascade Relationship Behavior in Microsoft Dynamics CRM

  1. Ashish Jha

    May 27, 2014 at 10:11 am


    Many users of CRM have been looking to move to Dynamics CRM 2013 from their previous versions. This new CRM comes in after 2 years and with a host of changes and new features which work well for different user sets and it also caters to solving many issues which was prevalent in Dynamics CRM 2011.

    There are many documented procedures for successful migration from CRM 2011to Dynamics CRM 2013, but here are some key points to remember.

    Once the upgrade is over, server cannot be rolled back to Dynamics CRM 2011.
    Upgrade from CRM 2011 to Dyamics CRM 2013 is supported from either RU6 or RU14. Recommended is to upgrade all deployments to RU14 before upgrading to Dynamics CRM 2013.

    Read More at:


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: