Recently we had to write a plugin that should trigger only when a user has manually associated the record from the form (N-N relationship). This was because we were also doing the same association through another plugin, in which case we didn’t want this new plugin to trigger. Here we can make use of ParentContext … Continue reading “ParentContext property of IPluginExecutionContext –…
Continue Reading Nishant Rana’s Article on their blog
ParentContext property of IPluginExecutionContext – Dynamics 365 / Dataverse
Recently we had to write a plugin that should trigger only when a user has manually associated the record from the form (N-N relationship). This was because we were also doing the same association through another plugin, in which case we didn’t want this new plugin to trigger.
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
Dyn365CE30 April 2024Use Geolocation Settings for Location Tracking and Auditing – Dynamics 365 Field Service
Dyn365CE29 April 2024Fix the trigger – Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found operand types ‘Edm.Guid’ and ‘Edm.String’ for operator kind ‘Equal’ (Power Automate / Dataverse)
Dyn365CE23 April 2024Portal does not load and displays “Server Error” or shows “Getting set up.. This might take a while” message -Portal Startup Issue (PowerApps Portal)
Dyn365CE22 April 2024Versioning and Drafts for Solution-based Cloud Flows – Power Automate
