Recently we had to disable plugin steps as part of data migration, below is the sample code we can use, either specify the name of the assembly, plugin, or plugin step as we are using the “begins with” condition or make changes as required. Hope it helps..
Continue Reading Nishant Rana’s Article on their blog
Sample Code – Enable / Disable Plugin Step (sdkmessageprocessingstep) Dynamics 365 / Dataverse
Recently we had to disable plugin steps as part of data migration, below is the sample code we can use, either specify the name of the assembly, plugin, or plugin step as we are using the “begins with” condition or make changes as required. class Program { static void Main(string[] args) { const string ConnectionString…
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
