Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Some cases are still reparented when an account is reassigned even if the cascade behavior is set to Cascade None in Microsoft Dynamics CRM 3.0

Some cases are still reparented when an account is reassigned even if the cascade behavior is set to Cascade None in Microsoft Dynamics CRM 3.0

View products that this article applies to.

Source: Microsoft Support
Back to the top

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION THAT IS CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED TO SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top

Symptoms

Consider the following scenario in Microsoft Dynamics CRM 3.0.
  • The cascade behavior for the account - case relationship is set to Cascade None.
  • You change the ownership of an account.
In this scenario, some cases that are associated with the account transfer the ownership to the new owner. However, other cases keep the original owner.

↑ Back to the top

Cause

This problem occurs because the following relationship links to the Case entity:
  • Account - Case
  • Contact - Case
Both relationships must have the cascade behavior set to Cascade None.

↑ Back to the top

Resolution

To resolve this problem, set the cascade behavior of the Contact - Case Parental relationship to Cascade None. To do this, follow these steps:
  1. Click Settings, click Customization, and then click Customize Entities.
  2. Double-click Contact, click Relationships, and then double-click the Contact - Case Parental relationship.
  3. Set the Type of Behavior value to Configurable Cascading.
  4. Set the cascade behavior for Reparent to Cascade None.
  5. Click Save and Close.
  6. Click Actions, and then click Publish.

↑ Back to the top

More information

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
923818� Changes to the Type of Behavior option in a relationship entity are not saved after you import customizations in Microsoft Dynamics CRM 3.0
933423� Behavior settings for a relationship are ignored in Microsoft Dynamics CRM 3.0

↑ Back to the top

Keywords: KB942683, kbexpertiseinter, kbmbsmigrate, kbexpertisebeginner, kbnomt, kbprb, kbtshoot, kbexpertiseadvanced, kbmbsservice

↑ Back to the top

Article Info
Article ID : 942683
Revision : 3
Created on : 2/22/2008
Published on : 2/22/2008
Exists online : False
Views : 291