function readOnly(count){ }
Don't have an account?
Search for an answer or ask a question of the zone or Customer Support.
You need to sign in to do that
Sign in to start searching questions
Signup for a Developer Edition
Sign in to start a discussion
What are recursive triggers. How can we avoid the recursion problem
Have you seen this?
http://developer.force.com/cookbook/recipe/controlling-recursive-triggers
And this
http://blog.jeffdouglas.com/2009/04/20/writing-bulk-triggers-for-salesforce/
Suppose i have one requirement
I want to update contact when account update so will write trigger OnAccount Update.
Same i want to update Account when Contact is update so i will write a trigger OnContact Update.
So when Account Update it will call => OnAccount Update Trigger and Contact is Updated...
When Contact is Updated ===> OnContact Trigger will Update Account ==>
So same chain will continue..
Account Update Contact
Contact Update Account
....
This can be avoid by Using static variable. In your trigger. If this will help you mark as solved. :)
Thanks
Nik's
Have you seen this?
http://developer.force.com/cookbook/recipe/controlling-recursive-triggers
And this
http://blog.jeffdouglas.com/2009/04/20/writing-bulk-triggers-for-salesforce/
Suppose i have one requirement
I want to update contact when account update so will write trigger OnAccount Update.
Same i want to update Account when Contact is update so i will write a trigger OnContact Update.
So when Account Update it will call => OnAccount Update Trigger and Contact is Updated...
When Contact is Updated ===> OnContact Trigger will Update Account ==>
So same chain will continue..
Account Update Contact
Contact Update Account
....
This can be avoid by Using static variable. In your trigger. If this will help you mark as solved. :)
Thanks
Nik's