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…

In Microsoft Dataverse and Dynamics 365, configuring a "Parental" relationship behavior automatically sets all cascading actions—including Assign, Delete, Share, Unshare, and Reparent—to "Cascade All." When the owner of a parent record is changed, the "Cascade All" rule for the Assign action ensures that the system automatically reassigns all associated child records to the new owner. This behavior enforces a strict dependency where the child records' ownership and lifecycle are entirely governed by the parent record, perfectly fulfilling the requirement to assign child records upon parent reassignment.

A. Referential, Restrict Delete: This behavior prevents the deletion of the parent record if child records exist, but it does not cascade the assign action to child records.

B. Referential: This behavior implies no cascading actions occur. Changing the owner of the parent record will not affect or reassign the associated child records.

C. Restrict: This is a specific cascading rule applied to the Delete action, not a comprehensive relationship behavior type that handles ownership reassignment.

1. Microsoft Corporation. (2023). Table relationship behavior. Microsoft Learn - Power Apps / Dataverse Documentation. Section: "Type of behavior", Paragraph 2 (Parental). Retrieved from official Microsoft Dataverse documentation detailing that the Parental behavior forces all cascading actions, including Assign, to Cascade All.

2. Microsoft Corporation. (2023). Create and edit 1:N (one-to-many) or N:1 (many-to-one) table relationships using Power Apps portal. Microsoft Learn. Section: "Relationship behavior", Table: "Standard behaviors". This section explicitly defines that under Parental behavior, any assignment of the parent record cascades to all related child records.