Temporarily prevent triggers occurring for DML operations

Question

I need to mass update 1000's of objects, which have triggers, but I don't want the triggers to run, as that brings me over the SOQL limit very quickly. I'm just trying to update via Anonymous.

So is it possible to stop triggers from occurring within a single transaction? Without modifying or disabling the triggers (this is a one time thing).

I've seen data import tools having the option of "prevent triggers", so I imagine it is possible without modifying the trigger or disabling it org wide....

Answer 1

The way I typically see this implemented is via a custom setting.

Create a custom setting of type hierarchy called Trigger_Disabled__c. Then you can create Account_Disabled__c, Contact_Disabled__c etc fields on it for the particular sobject instances you need to disable.

Why a hierarchy setting? You could use list custom settings as well, but if you wanted to disable workflows or validation rules as well, you can reference hierarchy custom settings in formulas.

Additionally, custom hierarchy settings will allow you to enable / disable the trigger for different users based on the organization hierarchy, etc.

In your trigger you would reference the trigger enablement check similar to below:

trigger AccountTrigger on Account(before insert){
    Trigger_Disabled__c triggerDisabled = triggerSettings.getInstance();
    if(triggerDisabled == null || !trigger.Disabled){
       //call your method or logic here
    }
}

Answer 2

You can deactivate your trigger anytime you want.Deactivate your trigger in your sandbox and deploy the trigger inactive to PRD. Be careful and notify your users / lock their access down so that there are no data inconsistencies during the time the trigger is inactive.

Answer 3

First Note: My answer is only applicable only if you could modify the triggers (which in your situation is not, but others might consider).

You can do this with a dummy User that should exist in your Sandbox/Prod Environment and only controlled by your Administrator or someone who should be able to update data without activating the Triggers.

• Create a dummy User and get its ID

• Modify the Trigger Code to have something like this:

  trigger TriggerName on SObject(before update, after update) {

      if (Trigger.isUpdate) {
  
          if ('theIdOfYourDummyAccount' != String.valueOf(UserInfo.getUserId()) {
              //All your update Trigger Code here
          }
      }
  

  }

Now if I am the administrator and you requested to be able to bypass the triggers while updating data, I'll give you the credentials of that dummy user. You'll login using that User to do your thing. Then I'll change the credentials afterwards.