[Applies to: Microsoft Dynamics CRM 4.0]
Find the latest SDK documentation: CRM 2015 SDK
When you create a hierarchical relationship you can control how the relationship behaves to support both data integrity and business rules for your organization. The relationship can control how actions that are performed on a parent record will cascade down to child records. For more information, see Cascading Rules.
The relationship type defines the cascading rules for a relationship. The following table describes the possible relationship types.
|System||A parental relationship type automatically defined by Microsoft Dynamics CRM for system entity relationships. You cannot modify this kind of relationship.|
|Parental||All operations on the parent entity instance are propagated to the child entity instances (cascade all):
|Referential||Operations are not cascaded between entities (cascade none):
|Referential, Restricted||The entity instance can only be deleted if it has no related entity instances. Otherwise, this relationship type is the same as referential.|
|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.|
Each entity can only participate as a related (referencing) entity in one parental or configurable cascading relationship. Most Microsoft Dynamics CRM system entities already participate in a parental relationship and this relationship cannot be changed. An entity can participate in multiple parental relationships as a primary (referenced) entity. There is no limit to the number of referential relationships that an entity may participate in.