-
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
8 Advantages of Using Salesforce For Small Businesses and Startups
Salesforce is one of the most powerful cloud-based CRM platforms. A robust yet efficient CRM system – one that meets all the field-specific needs of…
Algoworks Launches AWOM - A Salesforce App for Opportunity Management
Easier and efficient opportunities management in Salesforce CRM has been the unanswered prayer for many managers and sales organization alike, ever since the launch of…
Email Studio in Salesforce Marketing Cloud | The Ultimate Guide
Email Studio is a very important part of the Salesforce Marketing Cloud, it is used to build and send personalized emails from basic newsletters to…
Popular Salesforce Videos
Salesforce Sales Cloud Implementation
There are many things to take into consideration when developing and deploying a Salesforce Sales Cloud implementation that will take your business to the next…
Which Is Better Career Salesforce Admin or Developer?
Wondering Which is the better Career, Salesforce Admin or Salesforce Developer? Watch this video and join this group to learn all about it. Join this…
Add Intelligence to Any Salesforce App with Einstein Discovery
Bring intelligence in the context on any Force.com app thanks to the power of Einstein Data Discovery. Any Salesforce Admin or Developer can add in…
