Contact us today: (866) 4-WEBSAN (932726)                Get Instant Support

Monday, 27 August 2018 17:05

Know where your records are going with cascading rules

Written by

Everyone knows that Dynamics 365 has many great ways to link entities together, however once they are linked what controls do we have over their behavior? Enter, Cascading Rules. Cascading rules are a set it and forget it setting which controls the behaviors between two related entities. Cascading rules in D365 allows users to control what actions are passed down from one entity to another.

A great example where cascading rules come in handy is when users want to reassign the owner for a specific account record. However, they do not want its related activities such as emails, tasks and appointments to change owner when this happens. This is when you would go into cascading rules and update the assign setting to prevent the assign action from being passed down to its related activities.

In D365 the out of box settings for cascading rules, for a good majority of relationships, is Set to Parental (Cascade All), which means the action taken on the parent entity will be passed down. Now this may be suitable for some relationships, but in the case of the assign action being applied to Activities, this typically causes some undesirable results.

Cascade 1

Toggling the Type of Behavior to Configurable Cascading allows you to customize each of the relationship behaviors individually.

Cascade 2

Below are the possible cascading options you can select for each action.

Cascade 3

Cascade All: The action taken on the record will apply to its related entity records.

Cascade Active: Similar to Cascade All, except that the action taken on the record will apply to the related entity records, so long as the related records are in an Active or Open state. [Related records that have been deactivated will not be affected.]

Cascade User-Owned: Similar to Cascade All, except, that the action taken on the record will apply only to related entity records owned by the user.

Cascade None: The action taken on the record will not apply to the related entity records.

Now that you have learned about cascading options, why not apply it to your organization? Once cascading rules are setup properly, you never need to worry about related records being negatively impacted again. Email This email address is being protected from spambots. You need JavaScript enabled to view it. if you have any questions or need assistance implementing.

Leave a comment

Make sure you enter all the required information, indicated by an asterisk (*). HTML code is not allowed.