Salesforce Stack Exchange is a question and answer site for Salesforce administrators, implementation experts, developers and anybody in-between. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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....

share|improve this question
up vote 8 down vote accepted

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
share|improve this answer
Shannon Hale presented a great DF13 session explaining this in detail: – metadaddy Feb 4 '14 at 0:59
Not exactly what I need, is there a method to disable at transaction level rather than org/user level? – Mattisdada Feb 4 '14 at 3:06
If you are doing your mass updates as a single user, shouldn't hierarchical level control be sufficient? I don't think there is a way to turn it off otherwise unless you add a field to the record that tells the trigger to immediately end via code. – Michael Welburn Feb 4 '14 at 3:39
Thats fair enough, I've just seen data import tools being able to stop triggers with no modifications (why fill up classes with boiler plate when the overall app doesn't need it, DRY) to the triggers. So I'm assuming there is another way – Mattisdada Feb 4 '14 at 22:23
I marked this as the answer, as it is a good solution, but I still think there could be better ways, in my implementation I used the "early termination" method rather than a large if tree if(triggerDisabled!=null && triggerDisabled.Disabled__c){return;} – Mattisdada Feb 5 '14 at 0:21

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.

share|improve this answer
I don't want the triggers to be disabled for everyone, just during the one transaction while I mass update all objects. Disabling the trigger for everyone will cause data issues for us (triggers on this object is important) – Mattisdada Feb 3 '14 at 23:41

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.