Comments on: Apex Flow Control – Preventing Infinite Loops http://www.tehnrd.com/apex-flow-control-preventing-infinite-loops/ Force.com - jQuery - Technology - Life Wed, 08 Sep 2010 01:23:38 +0000 hourly 1 http://wordpress.org/?v=3.0 By: TRD http://www.tehnrd.com/apex-flow-control-preventing-infinite-loops/comment-page-1/#comment-657 TRD Tue, 23 Mar 2010 20:43:12 +0000 http://www.tehnrd.com/?p=272#comment-657 You saved the day! Good code and diagram. You saved the day! Good code and diagram.

]]> By: Coder312 http://www.tehnrd.com/apex-flow-control-preventing-infinite-loops/comment-page-1/#comment-325 Coder312 Fri, 18 Dec 2009 20:56:21 +0000 http://www.tehnrd.com/?p=272#comment-325 Great advice - thanks for sharing this! Your touch of humor helps the medicine go down :-) Great advice – thanks for sharing this! Your touch of humor helps the medicine go down :-)

]]> By: Jason http://www.tehnrd.com/apex-flow-control-preventing-infinite-loops/comment-page-1/#comment-217 Jason Fri, 09 Oct 2009 16:50:11 +0000 http://www.tehnrd.com/?p=272#comment-217 As chance may have it Jeff Douglas posted about this exact issue on the same exact day as me. The concept is the same but the code is a little different. Check it out here: http://blog.jeffdouglas.com/2009/10/02/preventing-recursive-future-method-calls-in-salesforce/ As chance may have it Jeff Douglas posted about this exact issue on the same exact day as me. The concept is the same but the code is a little different.

Check it out here: http://blog.jeffdouglas.com/2009/10/02/preventing-recursive-future-method-calls-in-salesforce/

]]> By: Jason http://www.tehnrd.com/apex-flow-control-preventing-infinite-loops/comment-page-1/#comment-214 Jason Fri, 09 Oct 2009 05:44:08 +0000 http://www.tehnrd.com/?p=272#comment-214 K1rk, you are correct. The utility.isFutureUpdate boolean will only stay true for the context of the current apex transaction. So if the @future method updates accounts which then causes additional triggers to execute they will all see this as true. As soon as all code has executed the value will return to null. K1rk, you are correct. The utility.isFutureUpdate boolean will only stay true for the context of the current apex transaction. So if the @future method updates accounts which then causes additional triggers to execute they will all see this as true. As soon as all code has executed the value will return to null.

]]> By: K1rk http://www.tehnrd.com/apex-flow-control-preventing-infinite-loops/comment-page-1/#comment-213 K1rk Thu, 08 Oct 2009 19:15:23 +0000 http://www.tehnrd.com/?p=272#comment-213 A great post. Can you clarify, however, how (or when) the static variable utility.isFutureUpdate becomes null or false again? I see where it's set to true in the futureMethods class... does it stay true globally (so the trigger sees it as true) only as long as that futureMethods class is still running? In other words, when futureMethods finishes, is that when isFutureUpdate becomes null again? A great post. Can you clarify, however, how (or when) the static variable utility.isFutureUpdate becomes null or false again? I see where it’s set to true in the futureMethods class… does it stay true globally (so the trigger sees it as true) only as long as that futureMethods class is still running? In other words, when futureMethods finishes, is that when isFutureUpdate becomes null again?

]]> By: Rajesh Shah http://www.tehnrd.com/apex-flow-control-preventing-infinite-loops/comment-page-1/#comment-201 Rajesh Shah Mon, 05 Oct 2009 11:13:30 +0000 http://www.tehnrd.com/?p=272#comment-201 Thanks. I always wondered how to use static variables to prevent Infinite loops. Now it is clear. Thanks. I always wondered how to use static variables to prevent Infinite loops. Now it is clear.

]]>