Timeline for Overwrite an SObject with another SObject without losing related records
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 5, 2016 at 4:26 | comment | added | Eric | Its may not be any more inefficient than the other options. In addition from a code perspective it is much less complex. Actually I think this is the perfect combination balance simplicity, reliability, and efficiency when compared to the other options. Of course, if you have all sorts of integrations, code, etc that occur due to a record insert and not an update (cause you would have to do that regardless) that could play into the decision | |
| May 5, 2016 at 4:20 | comment | added | Mossi | This is an option but I don't really want to insert SObject instances into the database just for the sake of merging them. Above all it consumes DML calls which is kind of inefficient and slow too. Appreciate the reply tho. | |
| May 5, 2016 at 1:30 | history | answered | Eric | CC BY-SA 3.0 |