Timeline for Why does upsert cause a DUPLICATE_VALUE error?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 14, 2019 at 10:03 | vote | accept | Sander de Jong | ||
| Jan 4, 2016 at 15:05 | comment | added | Sander de Jong | No, Name is not an external ID (please see another comment higher up in this page). Upsert should, by definition, be able to handle the upsert of something with an identical key value, it must behave as an update then, not as an insert. | |
| Jan 4, 2016 at 15:01 | comment | added | PepeFloyd | I am not sure I understand what you mean, from the code you posted, you are using the same external id in the same list in the same transaction, therefore, getting this error (which is expected) is there something missing from the code? | |
| Jan 4, 2016 at 14:48 | comment | added | Sander de Jong | The way I read this help page, is that it is about an individual upsert. And then the error message would make sense, provided that multiple keys already exist. But in my example, there is no match or only one. It looks like Salesforce checks the list for duplicate keys, but that would be strange. From the help page, it is not apparent to me that it performs this check. | |
| Jan 4, 2016 at 14:37 | history | answered | PepeFloyd | CC BY-SA 3.0 |