function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
zubair shareef mohammadzubair shareef mohammad 

controlling the execution of trigger

can we controll the execution of a trigger, If we create two triggers on the same object
Is there any way to control the execution order
Harish RamachandruniHarish Ramachandruni

What is two triggers you are are created and what is events . We can do it . 

If you have 2 triggers then there is no way to control the execution.
In order to control the execution, write a single trigger (best practice) and from trigger call your controller class. This way you will have full control over exeuction of your trigger.

Hope this helps.
zubair shareef mohammadzubair shareef mohammad
events are same like two before event on same objects
can we control that ??
Harish RamachandruniHarish Ramachandruni

So u can write in one trigger why are writing two triggres wahts is  sescenario now u have do do it .


No, even if the events are same, there is no control over which trigger will execute 1st. If you have same events in two different triggers, then merge them into a single trigger. If you can post snapshot if your coe, I can guide you in merging them.
zubair shareef mohammadzubair shareef mohammad
thank you !
Amit Chaudhary 8Amit Chaudhary 8

Please check below post for trigger

Trigger Best Practices | Sample Trigger Example | Implementing Trigger Framework

1) One Trigger Per Object
A single Apex Trigger is all you need for one particular object. If you develop multiple Triggers for a single object, you have no way of controlling the order of execution if those Triggers can run in the same contexts

Please check below post for framework
2) Logic-less Triggers
If you write methods in your Triggers, those can’t be exposed for test purposes. You also can’t expose logic to be re-used anywhere else in your org. 

3) Context-Specific Handler Methods
Create context-specific handler methods in Trigger handlers

4) Bulkify your Code
Bulkifying Apex code refers to the concept of making sure the code properly handles more than one record at a time.

5) Avoid SOQL Queries or DML statements inside FOR Loops
An individual Apex request gets a maximum of 100 SOQL queries before exceeding that governor limit. So if this trigger is invoked by a batch of more than 100 Account records, the governor limit will throw a runtime exception

6) Using Collections, Streamlining Queries, and Efficient For Loops
It is important to use Apex Collections to efficiently query data and store the data in memory. A combination of using collections and streamlining SOQL queries can substantially help writing efficient Apex code and avoid governor limits

7) Querying Large Data Sets
The total number of records that can be returned by SOQL queries in a request is 50,000. If returning a large set of queries causes you to exceed your heap limit, then a SOQL query for loop must be used instead. It can process multiple batches of records through the use of internal calls to query and queryMore

8) Use @future Appropriately
It is critical to write your Apex code to efficiently handle bulk or many records at a time. This is also true for asynchronous Apex methods (those annotated with the @future keyword). The differences between synchronous and asynchronous Apex can be found

9) Avoid Hardcoding IDs
When deploying Apex code between sandbox and production environments, or installing AppExchange packages, it is essential to avoid hardcoding IDs in the Apex code. By doing so, if the record IDs change between environments, the logic can dynamically identify the proper data to operate against and not fail

Let us know if this will help you