Recently, we had to write a small utility—a console application—that would go and update a bunch of existing records in our Dynamics 365 environment. However, we didn’t want any of my custom plugins to trigger during this update. Because the updates were internal, more like data correction / cleanup, and had nothing to do with business rules or processes enforced via plugins. Triggering them would’ve not only been unnecessary but could also lead to unwanted side effects like auto-assignments, email sends, or data syncing. Thankfully, the Dataverse platform provides us with two powerful properties that allow us to selectively bypass plugin execution logic.
BypassCustomPluginExecution – This allows us to bypass all the plugin steps for an operation – create, update, delete, etc.
BypassBusinessLogicExecutionStepIds – If we do not want to skip all the plugin steps, but just a few specific ones, we can use this property.
We have the below sample plugin registered that throws InvalidPluginExecutionException on the update of the lead record.
On updating the record through the console app, we will get the same exception.
To bypass all the plugins that are registered on Update, we can use the BypassCustomPluginExecution property as shown below.
To bypass only the specific plugin steps that are registered on Update, we can use the BypassBusinessLogicExecutionStepIds property as shown below.
One point to remember is these flags do not bypass system plugins or platform logic—only custom plugin steps we’ve registered.
This was a really handy trick in our recent utility and helped us to safely update the records without triggering the plugin. The other options could have been to either temporarily deactivate the plugin step, add certain conditions to the plugin based on calling user, flag/fields on the record etc.
No comments:
Post a Comment