-
Why we prefer one trigger per object in Salesforce?
Why we prefer one trigger per object in Salesforce?
-
2 Replies
-
Hii Anjali,
Best practice is not necessary "one trigger per object". It is one trigger per event and per object. An event is anything like before insert, before update, after insert....
You cannot update trigger code from an installed managed package. In this situation, you need to have your own trigger even if the package has already its own trigger on the same object and same event. -
We can write more than one trigger But it is not recommended. The best practice is One trigger On One object.
Log In to reply.
Popular Salesforce Blogs
10 Tips to Remember When Migrating from Goldmine to Salesforce
In the past few years, we have witnessed the surge in online CRM software, but nothing competes with Salesforce, not even GoldMine. Therefore, if you…
Introduction to Exception Handling in Salesforce Apex
Whenever you use a controller extension, extending a standard object, you can use the getRecord() to get the reference to the record. Most of us…
Apprentice to Salesforce Awesome Admin
Tell Us A Little About Yourself Brandon I was born in Manchester but spent much of my childhood and time at school traveling around the…
Popular Salesforce Videos
How to Configure SAML Single Sign-On with Salesforce as the Identity Provider
Configure single sign-on with a Salesforce org as the identity provider for an external Heroku app acting as the service provider, using SAML. Watch this…
Salesforce CPQ Bundles - Why You Need Them and How to Create a Bundle
Salesforce CPQ stands for Configure, Price, and Quote. This tool simplifies the whole process of configuring product bundles, pricing them, and generating quotes for customers.…
Salesforce Field Service: Complex Work and Routing | AblyPro Webinar
Salesforce Field Service is a powerful tool designed to help businesses manage complex field service workflows and optimize their routing processes. With Salesforce Field Service,…
