The 3 Most Important Salesforce Trigger Best Practices

It comes naturally that a Salesforce developer realizes that the initial apex trigger is limited or too small. This is especially true when your company growth demands new and varied needs. It is at this point that the trigger coding can become too complicated to handle and this will definitely need to be sorted out accordingly. Your Salesforce developers will need to tackle new functionalities and pairing the right logic with your trigger can become a nightmare. If that was not enough, any small change can render the trigger code a failure in which case you will have to develop another code from scratch. It is at this point you need to consider some Salesforce trigger best practices to implement.

 

Below is a compilation of the top 3 most important trigger best practices for Salesforce. Keep in mind that there are many but the insights below will highlight some of the key elements that must be put in place to attain ultimate success in this regard.

 

Trigger per Object is Enough

When learning how to customize Salesforce in this regard, using a single apex trigger per object is more than enough. This is definitely one of the most important Salesforce trigger best practices to keep in mind. Many triggers to handle just one object will just backfire. This is because you will lose control on the overall precedence. One trigger is good enough when it comes to handling the context combinations therein. The combinations include before insert, before an update, after an update, after insertion, after deletion, and after undeletion. You will not go wrong with this and anything else will not just lead to confusion, but it can have the system collapse. One trigger per object is, therefore, a key practice that cannot be overemphasized.

 

Logic-less Triggers are Ideal

This is one of the Salesforce trigger best practices that touches on vital Salesforce basics to know. It means that you need to delegate the necessary logic tasks to be executed by creating a handler class. There are several reasons why this is necessary. First, it is impossible to test a trigger that has a logic task in it. In addition, the logic task cannot be reused in your organization and hence cannot be exposed. In this regard, the trigger must be without logic to avoid problems and the handler class created will solve this problem accordingly.

 

Creating context-specific handler methods is among vital Salesforce trigger best practices

This is definitely another vital trigger best practice that should be implemented accordingly. When you need to add a new logic, you will create a new handler subroutine to the trigger to implement it. By doing this, you will find that the right handler method will be called at the desired time you have set.

 

There are many other best practices for Salesforce triggers that will come to play. However, the three practices mentioned above are the most important. Implementing them will ensure that your system is not overwhelmed; and that the organization functions optimally as it should.

Amanda McDonnald
Amanda is the Lead Author & Editor of Rainforce Blog. Amanda established the Rainforce blog to create a source for news and discussion about some of the issues, challenges, news, and ideas relating to Salesforce usage.
Amanda McDonnald on sabtwitterAmanda McDonnald on sabgoogle