web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Disable Plugin and Workflows for record being updated via mass update

(0) ShareShare
ReportReport
Posted on by

Hi,

I have the need to update possibly 1000's of records on one entity via a batch job that a user can kick off at any point.  While the job is updating those records we need to disable the plugins and workflows for those records only.  The key here is while this one user is mass updating their records others will be accessing other records that need the workflow and plugin to still run.

I see how to disable the workflow or plugin global via my batch job, but I can't figure out how to disable the workflow or plugin on an individual record basis?  

Thoughts so far:

1- Do this off hours, thus avoiding the need, may not be possible?

2- Put a flag on the record "Mass Update" and code the workflow and plugin to check that flag first, if checked stop if not continue.  We would flip that flag before we do mass updates on those records thus isolating them.

Other options?

Thank You.

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Alex Fun Wei Jie Profile Picture
    33,626 on at
    RE: Disable Plugin and Workflows for record being updated via mass update

    Hi,

    I would go for option 1, else you going to receive lots of support after that.

    For the option 2, not recommended , time consuming as you need to test in every single workflows and plugins.

    Unless you plan to do a mass update in future. It is always depend on the business scenario. Perhaps you can talk to business user.

  • Verified answer
    Arun Vinoth Profile Picture
    11,615 Moderator on at
    RE: Disable Plugin and Workflows for record being updated via mass update

    If you don’t need that plugin/WF functionality & whatever business logic they are doing for those records - then I would go with option1. As you can simply disable/deactivate them & proceeding after business hours will reduce the impact.

    Option2 need dev, deploy & regression test to make sure you didn’t break anything or introduce any new bugs in the system.

    We cannot skip plugin/WF only for particular records. Other option would be SQL update which is unsupported & impossible in CRM online.

    My vote is for 1

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
Aric Levin - MVP Profile Picture

Aric Levin - MVP 2 Moderator

#1
HR-09070029-0 Profile Picture

HR-09070029-0 2

#3
MA-04060624-0 Profile Picture

MA-04060624-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans