Avoid Recursive Trigger Calls In Salesforce

-



Recursion occurs when same code is executed again and again. It can lead to infinite loop and which can result to governor limit sometime. Sometime it can also result in unexpected output or the error “maximum trigger depth exceeded”. So, we should write code in such a way that it does not result to recursion.

For example, I’ve a trigger on Account object, which will be execute on before Update and after Update. In after Update I’ve some custom logic to update Account records. So, when I’m updating the Account records in After Update, it is throwing error “maximum trigger depth exceeded”. So, it is a recursion in apex trigger.

To avoid the situation of recursive call, we have to write code in such a way that the trigger will execute one time. To do so, we can create a class with a static Boolean variable with default value true. In the trigger, before executing the code keep a check that the variable is true or not.

Here in below trigger, I want to execute both before and after Update trigger only one time. I’m checking the static Boolean variable is true in both before and after Update trigger. In after update trigger changed the variable to false and after updating the account records, again changed the variable to true. In this way you can handle bulk of records in recursive trigger.

Apex Class:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
public Class AccountTriggerHelper{
    //Trigger execution check variable
    public static Boolean runOnce = true;
     
    //On before update
    public void onBeforeUpdate(map<Id, Account> mapNewAccount, map<Id, Account> mapOldAccount){
        //Write your logic here
        System.debug('Is Before Update');
    }
     
    //On after update
    public void onAfterUpdate(map<Id, Account> mapNewAccount, map<Id, Account> mapOldAccount){
        Update [SELECT Id, Name FROM Account WHERE Id IN: mapNewAccount.keyset()];
        AccountTriggerHelper.runOnce = true;
        System.debug('Is After Update');
    }
}

Apex Trigger:

1
2
3
4
5
6
7
8
9
10
11
12
13
trigger AccountTrigger on Account(before Update, after Update) {
     
    AccountTriggerHelper helper = new AccountTriggerHelper();
     
    if(Trigger.isBefore && Trigger.isUpdate && AccountTriggerHelper.runOnce){
        helper.onBeforeUpdate(Trigger.newMap, Trigger.OldMap);    
    }
     
    if(Trigger.isAfter && Trigger.isUpdate && AccountTriggerHelper.runOnce){
        AccountTriggerHelper.runOnce = false;
        helper.onAfterUpdate(Trigger.newMap, Trigger.OldMap);
    }
}

Debug Log:




Comments

Post a Comment

Popular posts from this blog

-
Image
  How to get the RecordType/Id Name of Account Object based on AccountId and Assign the Record Type Name to Lightning Component : Here are the steps on how to get the RecordType/Id Name of Account Object based on AccountId and Assign the Record Type Name to Lightning Component: Create a Lightning Component. In the component controller, add the following code: public with sharing class MyComponentController { Code snippet @AuraEnabled public static String getRecordTypeName(Id accountId) { SObject record = [SELECT Id, RecordTypeId, RecordType.Name FROM Account WHERE Id = :accountId]; return record.RecordTypeId == null ? null : record.RecordType.Name; } content_copy } In the component markup, add the following code: Code snippet <aura:attribute name="accountId" type="Id" /> <aura:attribute name="recordTypeName" type="String" /> <aura:handler name="init" value="{!this}" action="{!c.init}" /> &
Read more

Mapping of Flows in Salesforce

-
Image
What is Salesforce Flow? Flow is a powerful business automation tool that can manipulate data in Salesforce in a variety of ways. Such application can be created right from the org’s setup with just drag-drop/point-click. The ease of creating flows makes it the number one go-to tool when it comes to complex business requirements. It is not only easy to create, but also it does not require any coding. Beware! That does not mean you don’t need to know the Salesforce platform’s object relationships and overall how Salesforce runs. You have got to have (at least) mid-level understanding of SFDC and its features in order properly use flows. First, we are going to show how a flow is created and how it  flows  (it is a flow after all, isn’t it?). Flows can be created from Setup,  enter Flows in the Quick Find box, then select  Flows , and then click  New Flow .   When should I use Flows vs Process Builder? Flows and Process Builders are similar. Here are some of the key differences and simila
Read more
-
  How to split values from multiple picklist to dropdown value in salesforce LWC | Split and display multiple picklist value into single dropdown value in LWC | Create Lightning Web Component HTML Step 1 :-  Create Lightning Web Component : splitMultipicklistLwc.html SFDX:Lightning Web Component >> New >> splitMultipicklistLwc.html <template>     <lightning-card title="Split and display multiple picklist value in lwc ">         <table border="0" cellspacing="0" cellpadding="0" class="slds-table slds-table_bordered slds-table_col-bordered" style="border-collapse:collapse;">             <tr for:each={oppItemArr} for:item='recItem' key={rowId} for:index='index' >                                <td>                     <div class="slds-form-element_controller">                         <select style="margin-top: 15px;" class="slds-select&quo
Read more