Order of Execution (Rules, Triggers etc.) in Salesforce

-
Order of Execution
1. Record is Created/Loaded.
2. Trigger.New is populated.
3. System Validations are executed.
4. Before Trigger runs.
5. Custom Validations are executed.
6. Record is Saved, not yet committed.
7. After Trigger runs.
8. Assignment/Auto Response Rule runs.
9. Workflow Rule are executed.
10.Escalation Rule runs.
11.Before/After trigger are executed.(based on step 9)
12.Record is committed to Database.
13. Roll up
14. Criteria Based Sharing Rule
15. Post commit logic is executed.

Comments

Post a Comment

Popular posts from this blog

Cascade deleting too many records

-
Cascade deleting too many records DELETE_OPERATION_TOO_LARGE:Cascade deleting too many records This is because there are too many records or related records to be deleted, which cannot be stored in Recycle Bin. For example: I faced this issue while deleting Opportunity, altough there were only few Opportunity but there were many related Opportunity Line Item and Schedules. 1. Emptying the Recycle Bin/Org Wide Recycle Bin can be one solution, or contact Salesforce to permanently delete Org Wide recycle bin. 2. Perform Hard Delete and this requires "Bulk Api Hard Delete" permission. 3. Contact Salesforce.com to get the Enables cascade delete. Read the article for "Activation of Bulk API Hard Delete on System Administrator profile" https://help.salesforce.com/articleView?id=000171306&type=1 But even this did not solve the issue. Solution: Reduce the batch size: 50 In a many-to-many relationship, a user can't delete a parent record if there are more than...
Read more