Check and Set Assign Cascade Relationship Behavior for Microsoft CRM


I would like to talk about an important Microsoft CRM design setting: Cascade Relationship Behavior.
 
Scenario: What happens to the Account’s child records (Contacts, Opportunities, Activities, History, etc.) ownership if we reassigned the Account to another owner?  If I have a CRM account record "ABC, Inc." with an initial ownership of "Owner2" and I then reassigned the "ABC, Inc." account record to "Owner3" – what effect does this have on the ABC, Inc.’s child records ownership? 
 
Answer: Under the default Microsoft CRM 4.0 (OnPremise) and CRM Online setting – they will all be reassigned to "Owner3".
 
Account Owner2:
Reassigned to Owner3:
 
All ABC, Inc.’s child contacts are reassigned to "Owner3": 
 
Same for all of ABC, Inc.’s child activities – they are all reassigned to "Owner3": 
 
Same for all of ABC, Inc.’s child history – reassigned to "Owner3" and so on for all other ABC, Inc. child records
 
An important note is that for CRM History records (activities that are completed) or any other "completed" record types such as CRM Opportunities, Leads, Cases, etc. – we should keep the data intact and not change the Owner info since it should be considered "historical" data. 
 
So, if this is not the desirable initial setting, how do we change it?
 
Answer:  This setting can be updated under the "Relationship Behavior" section in the Account customization (CRM Client >> Settings >> Customization >> Account >> select the child record type under "Related Entity"):
 
Under the "Relationship Behavior" section, change the "Type of Behavior" from "Parental" to "Configurable Cascade", select a different action for the "Assign" cascade behavior.  The default is "Cascade All".
 
 
There are four actions to select from: "Cascade All", "Cascade None", "Cascade Active", and "Cascade User-Owned".  "Cascade None" is the most conservative.
 
 
Review the Assign Cascade Relationship Behavior for other child record types and select the desired behavior setting.  Be sure to save and then publish your customization afterwards.  Repeat this for other CRM entities such as Contact, Lead, Opportunity, Case, etc.

 
 
 
Contact us if you need help with your Microsoft CRM.  Free Estimate.
 
Frank
Workopia, Inc.
Microsoft Dynamics CRM MVP

Follow Workopia on Twitter

FREE 30-Day Trial, Setup & Training – Microsoft CRM Online
 Sign up for a FREE 30-Day Trial, Setup & Training

Advertisements

About Microsoft Dynamics CRM Online

Microsoft Dynamics CRM and CRM Online specialist. Microsoft CRM MVP since 2006
This entry was posted in Microsoft Dynamics CRM. Bookmark the permalink.

9 Responses to Check and Set Assign Cascade Relationship Behavior for Microsoft CRM

  1. Pingback: Danger of Reassign ALL Records Owned by the Current User function | Microsoft Dynamics CRM Online Blog

  2. Misty says:

    Did this fix work for keeping the history of the orginal owner of the opt? Thanks

  3. When setting are changed/published – it will affect the behavior going forward. Previous value remain the way the were until another assign event.

    • Misty says:

      Our scenario is we have an account with contacts, opportunity/s, history, activities with sometimes a few users with that data and they assign the account to someone new we want that original opportuinity or contact to stay with the original owner even the closed ones. Currently it will reassign everything to the new owner of the account. So i ran into this blog and was wandering if it would solve our issue of that.
      So from my understanding there is no way around of the reassingment of an account for the opportunties, contacts, history to stay with the original owner/s instead of being all to the new account owner.

      • Yes, this is supported via updating the cascade setting for Account and Opportunity to “Cascade None”:
        Setting can be updated under the “Relationship Behavior” section in the Account customization (CRM Client >> Settings >> Customization >> Account >> select the child record type under “Related Entity”)

  4. Pingback: Danger of Reassign ALL Records Owned by the Current User function - Workopia Microsoft CRM & CRM Online Blog - CRM Technical Blogs - Microsoft Dynamics Community

  5. Roger says:

    Following these instructions worked great for changing the assign behavior on history entities, however when the account is reassigned, the new owner can no longer see the history (they don’t own it). Shouldn’t the new owner inherit rights to the old activities since they own the account?

  6. Lior P says:

    Thanks!

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s