Has anyone ever, anywhere, seen the Apex Exception "Cannot set the value of a calculated field"

Question

And no, if you're thinking I'm writing to a formula field, that's not it - read on....

I've been seeing this error sporadically during an upsert on one, and only one, org.

Upsert failed. First exception on row 0 with id a1H00000000VR5lEAG; first error: UNKNOWN_EXCEPTION, Cannot set the value of a calculated field: []

I've done a search for "Cannot set the value of a calculated field" (in quotes) and, believe it or not, it comes up with just one unrelated response.

And no, it's not the obvious - I'm not setting the ID, and if you try to update a formula field, you get the error "Field is not writable" which, as you would expect, returns gazillions of hits when searched.

In terms of being sporadic - it might appear once every week or two. So we're talking maybe one error in >100K upserts on this object. On this one org - nowhere else.

Notice that it doesn't actually say what field is impacted. And, to add to the confusion - this is an upsert of a custom object in a managed package. There are no triggers or workflows on the object.

I'm very much at a loss - without the ability to reproduce it, contacting SFDC support is likely to be a waste of time. So, if anyone has seen this before and has any suggestions or context to provide, I'd greatly appreciate it.

Dan

If/when you catch the DMLException can you use the getDmlFieldNames() method to help isolate the fields. Maybe throw another exception and include the full sObject that was being inserted (Convert to JSON and append to the message). — Daniel Ballinger, Apr 02 '14 at 08:19
If the error is presented in a page and that org can be left in "Development Mode" (http://salesforce.stackexchange.com/questions/30094/no-log-for-visualforce-errors#30097) until the error occurs then the stack trace information output might help. — Keith C, Apr 02 '14 at 11:52
I have to wonder if there isn't a field that requires encryption that's being upserted without first being encrypted. That might produce an error along those lines. I'd be looking at the types of fields on the object to see what's there that might be in the wrong format or requiring special handling of some sort like encryption. Tough one for sure. — crmprogdev, Apr 02 '14 at 12:36
I'm curious to learn if you got anywhere with this issue. Did SF Support provide any info around the error message? — smohyee, Aug 31 '15 at 15:57
Wow - I'd forgotten all about this one. I haven't seen this error in a while, so I'm guessing whatever it is was some obscure platform bug that has since been resolved. Either that, or I shoved it into a try/catch block and am now ignoring it :-) — kibitzer, Sep 01 '15 at 18:35
It may be due to rollup summary field please check there that rollup summary field exist or not. — Ravikant Kedia, Oct 07 '15 at 02:53

score 2 · Answer 1 · answered Dec 20 '15 at 05:58

2

This was indeed a bug.

I have looked up the related investigations and bug report, and it was resolved in Summer 15.

answered Dec 20 '15 at 05:58

pchittum

19,701
5
54
97

4

It's back, this time in the context of trying to be clever and use Formula.recalcuateFormulas() (Winter '20 feature) in a BEFORE trigger (Salesforce doesn't seem to like proceeding to the DML with SObjects that have populated formula field values). – k.. Nov 22 '19 at 00:04

Juan Alvarez · Answer 2 · 2021-02-15T17:54:28.017

As @k.. mentioned, this also happens when using Formula.recalculateFormulas(Trigger.new) in a before trigger, but only for non-checkbox formulas:

I tested:

Checkbox formula TRUE and FALSE: both pass.
Text formula Hello: fails.
Date formula DATE(2021,1,1): fails.
Number formula 42: fails.
Currency formula 11.22: fails.

I could not find a report for this issue and I have a dev account, so I can't report bugs. Could any of you do it?

The only workaround I have found without using a query is to clone the records.

List<Custom_Object__c> objectsWithRecalculatedFormulas = new List<Custom_Object__c>();
for(Custom_Object__c newObject : Trigger.new) {
    objectsWithRecalculatedFormulas.add( newObject.clone(true) );
}
Formula.recalculateFormulas(objectsWithRecalculatedFormulas);

Has anyone ever, anywhere, seen the Apex Exception "Cannot set the value of a calculated field"

2 Answers2

Linked

Related