Comments on: Preventing Recursive Future Method Calls in Salesforce http://blog.jeffdouglas.com/2009/10/02/preventing-recursive-future-method-calls-in-salesforce/?utm_source=rss&utm_medium=rss&utm_campaign=preventing-recursive-future-method-calls-in-salesforce Get your head out of your #@! and into the clouds! Wed, 08 Feb 2012 07:57:55 +0000 hourly 1 http://wordpress.org/?v= By: Alex S. http://blog.jeffdouglas.com/2009/10/02/preventing-recursive-future-method-calls-in-salesforce/comment-page-1/#comment-2103 Alex S. Wed, 24 Nov 2010 17:16:40 +0000 http://blog.jeffdouglas.com/?p=1396#comment-2103 Jeff, have you encountered any good workarounds for the issue you identified with a managed package's future methods being called from another managed package's future method through a trigger? Jeff, have you encountered any good workarounds for the issue you identified with a managed package’s future methods being called from another managed package’s future method through a trigger?

]]> By: Ezra http://blog.jeffdouglas.com/2009/10/02/preventing-recursive-future-method-calls-in-salesforce/comment-page-1/#comment-1377 Ezra Wed, 04 Aug 2010 19:35:18 +0000 http://blog.jeffdouglas.com/?p=1396#comment-1377 quite handy! I'm fiddling with @future now, and if I understand the error messages correctly, I need to rewrite my test classes, too. Is there a good resource for writing test classes for @future classes? quite handy! I’m fiddling with @future now, and if I understand the error messages correctly, I need to rewrite my test classes, too. Is there a good resource for writing test classes for @future classes?

]]> By: Jeff Douglas http://blog.jeffdouglas.com/2009/10/02/preventing-recursive-future-method-calls-in-salesforce/comment-page-1/#comment-287 Jeff Douglas Fri, 05 Feb 2010 21:05:51 +0000 http://blog.jeffdouglas.com/?p=1396#comment-287 I believe that each request is atomic. Therefore, I think everything will reset for each batch. The static variable is in context for EACH trigger request. I believe that each request is atomic. Therefore, I think everything will reset for each batch. The static variable is in context for EACH trigger request.

]]> By: Deepak http://blog.jeffdouglas.com/2009/10/02/preventing-recursive-future-method-calls-in-salesforce/comment-page-1/#comment-286 Deepak Tue, 02 Feb 2010 08:00:38 +0000 http://blog.jeffdouglas.com/?p=1396#comment-286 First of all thanks for your wonderful examples that really has saved lot of efforts so many times. I have a question here if we are using the second approach and will do the bulk operation from Data loader than we know tha static variable sets for one complete Batch size, in that case when the trigger will fire for second record it will get the static variable updated and will not fire the trigger. Am i right? First of all thanks for your wonderful examples that really has saved lot of efforts so many times.

I have a question here if we are using the second approach and will do the bulk operation from Data loader than we know tha static variable sets for one complete Batch size, in that case when the trigger will fire for second record it will get the static variable updated and will not fire the trigger.

Am i right?

]]> By: jeffdonthemic http://blog.jeffdouglas.com/2009/10/02/preventing-recursive-future-method-calls-in-salesforce/comment-page-1/#comment-285 jeffdonthemic Fri, 09 Oct 2009 17:57:56 +0000 http://blog.jeffdouglas.com/?p=1396#comment-285 No problem! Yours is probably better than mine anyway! No problem! Yours is probably better than mine anyway!

]]> By: Jason http://blog.jeffdouglas.com/2009/10/02/preventing-recursive-future-method-calls-in-salesforce/comment-page-1/#comment-284 Jason Fri, 09 Oct 2009 16:36:26 +0000 http://blog.jeffdouglas.com/?p=1396#comment-284 Ha, I posted about this same thing on the exact same day. I didn't copy you, I promise :-). Great minds think alike I suppose. Ha, I posted about this same thing on the exact same day. I didn’t copy you, I promise :-) . Great minds think alike I suppose.

]]>