Contents
How do you Bulkify codes?
Best Practice #1: Bulkify your Code When a batch of records initiates Apex, a single instance of that Apex code is executed, but it needs to handle all of the records in that given batch. For example, a trigger could be invoked by an Force.com SOAP API call that inserted a batch of records.
What is Recursive trigger How do you avoid Recursive triggers?
Handle recursion – To avoid the recursion on a trigger, make sure your trigger is getting executed only one time. You may encounter the error : ‘Maximum trigger depth exceeded’, if recursion is not handled well.
What are the best practices for bulkify trigger?
Salesforce Trigger Best Practices and Bulkify Trigger Bulkifying is the process of designing code modules so that they can handle large quantities of data in a single call or calculation, rather than individual data sets over repeated calls from a higher code body.
What does it mean to bulkify a code module?
Bulkifying is the process of designing code modules so that they can handle large quantities of data in a single call or calculation, rather than individual data sets over repeated calls from a higher code body.
What does it mean to bulkify Apex code?
Bulkifying Apex code refers to the concept of making sure the code properly handles more than one record at a time. An individual Apex request gets a maximum of 100 SOQL queries before exceeding that governor limit. So if this trigger is invoked by a batch of more than 100 Account records, the governor limit will throw a runtime exception
Why do you need to bulkify a trigger in rainforce?
In bulkifying, you’re improving efficiency of the code being run, as each time something has to be called to handle a task, such as a trigger or a class, it has to be loaded in and out of memory, and each returned result has to be added to a collection after the fact, in your higher level namespace. So, how is bulkfying done?