-
Describe the benefits of the “One Trigger per Object” design pattern?
Describe the benefits of the “One Trigger per Object” design pattern.
-
1 Reply
-
Hi Manpreet,
It's best Practice to have one trigger per object,If you assign more than one trigger per object then the order of execution of Triggers on object is not defined,you can't predict which trigger will run first therefore required result will not be achieved.
Log In to reply.
Popular Salesforce Blogs
Best Practices for Salesforce Lightning Web Components (LWC)
Always Name Carefully Always name variables, methods, and components carefully. Do not start a property name with ‘on’, ‘aria’, or ‘data’. Do not use reserved…
The significance of Salesforce and Facebook Integration
Facebook is a leading social networking app in today’s market scenario for doing tasks like share updates, photos or videos with friends and community. Salesforce…
Master the Art of Customer Service with Case Management | Salesforce
What is the top priority for any business today? If you anticipated it as ‘Customer Experience’, you are probably right. Recent research found that nearly…
Popular Salesforce Videos
Introduction to Salesforce Commerce Cloud for Developers
Commerce Cloud powers e-commerce for many of the world's leading brands and it represents a great opportunity for developers around the world. Join us to…
How does Salesforce Field Service Platform increase servicing revenue for your company
CRM Salesforce, along with its Field Service Lightning App, is drastically improving the field-force productivity in the industry. Built on the Salesforce Service Cloud, it…
Top 5 FAQs' of Salesforce Commerce Cloud
Salesforce Commerce Cloud, formerly known as Demandware, is a user-friendly and streamlined e-Commerce platform designed with a simple goal to help a company expand its…
