-
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. - [adinserter block='9']
-
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
Best Automation Testing Training in Electronic City, Bangalore
Looking for the Best Automation Testing Training in Electronic City, Bangalore to build a high-growth IT career? Join eMexo Technologies, the Top-Rated Automation Testing Training Institute in Electronic…
What is Pardot in Salesforce and Does Your Business Need it in 2024?
Many businesses consider marketing automation to be a must-have. According to the latest Salesforce State of Marketing Report, the average enterprise has 900 (!) different applications…
Role of Salesforce in Successful Small Business
Customer connections are critical to your company's success, therefore you must manage them as efficiently as possible. The technology can help you connect with customers…
Popular Salesforce Videos
Alias Tags and Tracking in Salesforce Marketing Cloud
Cameron Robert from Datarati demonstrates how the Alias tag works in Salesforce Marketing Cloud, and how you can use it to improve your email tracking…
Learn About How to Set Profiles in Salesforce?
Learn about Profiles in Salesforce and types of profiles, Standard and Custom Profiles. Watch this video and do let us know in the comment section…
Salesforce Data Loader Tutorial
The Salesforce Data Loader is an easy to use graphical tool that helps you to get your data into Salesforce objects. The Data Loader can…
