Hi Avanish,
If the record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the parent record. Parent record goes through save procedure. So, updating the child inputs to a roll-up summary field can cause a trigger on an object to fire.
Consider the following example with a Master detail between Child and Parent and the following:
- Number field on Child called Num Field
- Roll-up summary on Parent that sums Num Field
Write the following trigger on Parent__c:
trigger ParentTrigger on Parent__c (before update) {
for (Parent__c p : Trigger.New) {
p.addError(‘Not going to save’);
}
}
Now go into the new or edit page for your Child object and fill in a value for Num Field and save the record and see what happens. You get:
Error: Invalid Data.
Review all error messages below to correct your data.
Not going to save
Next, blank out the Num Field and save and see what happens. No error is generated and the Childsaves.
So when the child record is saved and the field feeds into the roll-up summary the parent trigger is executed.
Thanks