We’re rewarding the question askers & reputations are being recalculated! Read more.
Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options answers only user 2995
1
vote
It means you should be using CheckRecursive.runOnce instead of cr.runOnce. system.assert(CheckRecursive.runOnce()); system.assert(!CheckRecursive.runOnce());
answered Oct 4 '16 by Adrian Larson
2
votes
If you are adding child records in a before trigger when there is a rollup summary field, you will experience this issue. Simply move the application of this logic to an after trigger. It's one of the …
answered Jul 27 '16 by Adrian Larson
4
votes
You can only enqueue one job from a job (be it Batchable or Queueable). There are pretty much exactly two reasons you would run into this error. Either XFTY_DummySObjectSupplier kicks off a Queueable …
answered Jul 26 by Adrian Larson
4
votes
in this way, you do not even need a static flag to block recursion, because you will not cause update trigger re-entry. There are two types of triggers: Before triggers are used to update …
answered Jan 13 '17 by Adrian Larson
1
vote
If none of the formulas reference anything cross-object, you should be good. If you have any trouble referencing it directly, you can call recalculateFormulas() to ensure you have the correct value.
answered Oct 12 '17 by Adrian Larson