10 Prevent Recursion while implementing Apex Trigger in Salesforce

10 Prevent Recursion while implementing Apex Trigger in Salesforce | Learn Salesforce Development

Рет қаралды 18,407

Күн бұрын

Пікірлер: 10

@SanjayGuptaTechSchool 2 жыл бұрын

For Online Individual or Group Training Please Email or Visit below Website. Email: sanjaygupta.techschool@gmail.com or Visit: studysalesforce.com/ Connect with Sanjay Gupta on Linkedin: www.linkedin.com/in/sanjay-gupta-bb2a79bb/ Udemy : Enroll Salesforce Flow Builder Masterclass: kadge.io/flowbuilder Udemy : Enroll Salesforce Admin Certification Masterclass : kadge.io/admin201 Udemy : Enroll Salesforce PD1 Certification Masterclass : kadge.io/pd1 Please like and subscribe to support the efforts.

@shivadumnawar467 3 күн бұрын

Thank you so much sir.

@sarulatha5006 2 жыл бұрын

Why we are using after event,as this is only updating account Record.Cant we use before event

@SanjayGuptaTechSchool 2 жыл бұрын

Actually after saving the record we need to do one more dml that is why.

@sedentaryhooman 10 ай бұрын

For more than 200 records update, your trigger won't behave in the expected way.. first batch of 200 records will call your handler class but the other set of batches won't be executing your handler class logic because at that point of time your static variable has already changed its value. Trigger runs in the batch of 200 records as we know. This is not a perfect solution to stop recursion! 🙂

@hekkelkelseheklalallkh8161 8 ай бұрын

Yeah right, This is just a temporary fix assuming that the bulk records size will be always less than 200. Apart from this, I have come across static set() and static map() to avoid recursion, but I am a little confused with them. which method do you think is better for this?. Also please share with me if you know any other method to avoid recursion.

@sedentaryhooman 8 ай бұрын

@@hekkelkelseheklalallkh8161 This are the only ways to avoid.. i.e. static Boolean variable, static set and static map. Static map is considered to be the best way to avoid it.

@apoorvamishra2499 Жыл бұрын

getting an error - after_update_trigger: execution of AfterUpdate caused by: System.FinalException: Record is read-only Class.after_update.update_recursion, how to resolve?

@TwoIndiansReact Жыл бұрын

Make a List and in the list Give Reference of id like this in ur Trigger :- Trigger TriggerName on Account(After Update) if(Trigger.isAfter && Trigger.isUpdate){ ListAccList = [SELECT id , Description From Account]; AccountTriggerHandler.UpdateAccount(AccList , Trigger.oldMap);