5

We have to do a major data migration on a customer org using our ISV product. We need to delete and insert large amounts of records who in some cases have complex triggers.

Is there a way to temporarily deactivate a packaged trigger that doesn't require coding?

Would it be possible to deactivate those triggers in a patch release and then just push that to a single customer org?

Any other idea are welcome.

1
  • 1
    Not an easy thing to do.. What about enhancing your product by including a custom setting in which you can deactivate your packaged triggers? Might make more customers happy if they have that in their own hands.. – Guy Clairbois Feb 10 '14 at 20:56
4

You can make a patch with the trigger deactivated and push it to just that org, but that's not a long-term solution.

It looks like your product needs an enhancement to allow trigger deactivation in certain circumstances - use a hierarchy custom setting so that the triggers turn off for the integrating user and continue to work for the rest of the company.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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