Rajeev Pentyala – Technical Blog on Power Platform, Azure and AI

Assume the relationship behavior between ‘Contact’ and ‘Appointment’ is “Cascade All” on ‘Assign’ action.

By virtue of that, if a Contact has 2 Appointments, if I change the owner of ‘Contact’ the related 2 Appointment owner also changes.

In one of the requirement, we have to restrict the Cascade operation based on business logic on child record (i.e.,  Appointment)

So I registered a Plugin on ‘Assign’ of ‘Appointment’ and want to handle the Cascade operation, but the Plugin never get executed.

Reason & Solution

• CRM treats Cascade Assign operation on Child records as an Update.
• Register the Plug-in on ‘Update’ instead of ‘Assign’ message.
• In the Update plug-in, the Target entity only contain ‘Owner’ field

🙂