Remove custom Resource Hero triggers from a production org

When setting up Resource Hero on a custom object, you are required to create an Apex trigger. If at some time in the future you need to uninstall Resource Hero, you must first remove these custom triggers. Details on how to remove custom Resource Hero triggers from a production org can be found below.

To summarize, you would create a zip file that contains two files, package.xml and destructiveChanges.xml.

If you need to remove a trigger called MyCustomObjectTrigger, this is what your two files should look like:

Package.xml

<?xml version="1.0" encoding="UTF-8"?>
<Package >
   <version>37.0</version>
</Package>

destructiveChanges.xml

<?xml version="1.0" encoding="UTF-8"?>
<Package>
   <types>
      <members>MyCustomObjectTrigger</members>
      <name>ApexTrigger</name>
   </types>
</Package>

This zip file can then be deployed using Workbench or the Force.com Migration Tool.

Related Support Posts:

Ready to get started?

Schedule a call to see if Resource Hero is right for you

Book now