PL-200 · Question #36
You create a parent entity and a child entity. The parent entity has a 1:N relationship with the child entity. You need to ensure that when the owner changes on the parent record that all child…
The correct answer is A. Parental. Parental relationship behavior in Dynamics 365 cascades all major actions - including Assign (ownership change) - from the parent record to all related child records. This is exactly what is needed: when the owner of the parent changes, all child records are automatically…
Question
Exhibit
Options
- AParental
- BReferential, Restrict Delete
- CReferential
- DRestrict
How the community answered
(22 responses)- A95% (21)
- D5% (1)
Explanation
Parental relationship behavior in Dynamics 365 cascades all major actions - including Assign (ownership change) - from the parent record to all related child records. This is exactly what is needed: when the owner of the parent changes, all child records are automatically reassigned to the new owner. Referential (C) behavior does not cascade any actions; child records are simply unlinked if the parent is deleted. Referential, Restrict Delete (B) prevents parent deletion when children exist but does not cascade ownership. 'Restrict' (D) is not a standard standalone relationship behavior type for this purpose.
Topics
Community Discussion
No community discussion yet for this question.
