News and Announcements icon

Dynamics 365 CommunityForums Dynamics 365 general forum Changes relationship b...

Dynamics 365 general forum

Suggested answer

Changes relationship behavior: why does it not affect previous records?

(0) Share

Report

Report

Posted on by Joel D

355

Hi,

I'm investigating the N:1 Relationship Account to Order for the entity Order.

Can you please explain what happens when I change the Relationship Behavior from Parental - Cascade All to Cascade None?

After the change, the Account's owner can't see the future orders from someone else associated with it, unless he/she has been assigned other permissions, or belongs to the same Teams.

But the owner of the Account will see the old records (orders that were saved when the type of behavior of the relationship was "Parental"). Why doesn't the change affect the old records? Is there a way to overcome the issue?

Categories:

Customization / Solutions / SDK and API

Dynamics 365 Administration

All responses Img

All responses (1)

Answers Img

Answers (0)

Suggested answer

Nya 29,050 on at

Like (1)

Report

RE: Changes relationship behavior: why does it not affect previous records?

Hi,

Please refer to the following blog about "From Cascade ALL to Cascade None".

(+) Usage/Significance of configurable cascading behavior of the type ASSIGN [From Cascade ALL to Cascade None] during data migration. - Microsoft Dynamics CRM Community

It explains in detail the difference in behaviours brought about by the two options and the specific scenarios in which they can be used.

You can substitute Opportunity for Account and Activity for Order, which makes it easy to understand.

Helpful resources

Quick Links

Leaderboard

#1

André Arnaud de Cal... 288,768 Super User

#2

Martin Dráb 225,985 Super User

#3

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans