Considerations while implementing a Trigger

Considerations while implementing a Trigger

* Upsert trigger fires on 4 different events:- before(insert, update), after (insert, update)

** Merge trigger is fired on both events on delete

*** Field history is updated after the trigger has successfully finished processing data.

**** Any callout should be asynchronous so that trigger does not have to wait for the response.

***** A trigger cannot have a static keyword in its code.

****** If a trigger completes successfully the changes are committed to the database and if it fails                                                                                                         the transaction is rolled back.




*** Trigger Most Common Interview Questions and Answers for MNCs and Small-Mid Companies ***


Visualforce Most Common Interview Questions and Answers for MNCs and Small-Mid Companies ⇒ *** Comming Soon ***

Apex Most Common Interview Questions and Answers for MNCs and Small-Mid Companies ⇒ *** Comming Soon ***


Lightning Component Most Common Interview Questions and Answers for MNCs and Small-Mid Companies ⇒ *** Comming Soon ***



Lightning Design System Most Common Interview Questions and Answers for MNCs and Small-Mid Companies ⇒ *** Comming Soon ***


Freelancing Services At Salesforce: Freelancing Services


For Job Support click this URL: Job Support


Comments

Popular posts from this blog

Trigger Update Contact record using trigger when account record is updated

If you looking for Salesforce Certified Freelancer for you Salesforce org works feel free to contact us, details are in below:

Context variables in triggers