2020年12月11日 · As per the design considerations, the SavePoint is used to avoid the caller catching exceptions (perhaps resulting from the second DML statement). That would then result in the Apex runtime committing updates to the opportunity lines (first DML statement), causing a partial update to the database.

Apex gives you the ability to generate a savepoint , that is, a point in the request that specifies the state of the database at that time. Any DML statement that occurs after the savepoint can be discarded, and the database can be restored to the same condition it was in at the time you generated the savepoint.

2023年11月3日 · N.B. while the fflib UnitOfWork pattern does implement wrapping multiple DML operations within a savepoint; it does not support partial success OOTB (i.e. allorNothing=false). You have to delegate to an IDoWork handler for partial success operations and then it still is complicated when you have a batch of inter-related object DML in the Unit ...

2016年11月14日 · With the Savepoint, they all work together as a transaction. Without it, the other two DML Operations in your transaction succeed even if the third fails. The only way the code will behave the same after removing the Savepoint is the case where you get a failure before or during insert someRecords. Which Operation Fails? Use Savepoint? insert ...

2016年7月11日 · Apex gives you the ability to generate a savepoint, that is, a point in the request that specifies the state of the database at that time. Any DML statement that occurs after the savepoint can be discarded, and the database can be restored to the same condition it was in at the time you generated the savepoint.

It turns out having the Savepoint in the static memory is fine as long as the trigger is executed once. But regardless of whether we are in test mode the TypeException is thrown when the trigger is executed twice. Ashwani's comment helped me realize this: There is difference in Transaction and Context. Savepoint are for transaction only.

Setting database.savepoint in one method and rolling back in another method I have three objects ObjectA, ObjectB, ObjectC. ObjectA is the grand parent, ObjectB is child of A & Object C is child of B.

Savepoints are for when you are performing a bunch of operations, and if one operation fails, you want to restore the system to a consistent state rather than allowing them to commit independently of each other. If it is just records in a Database.update, you don't need a savepoint. Salesforce rolls back by default on failure. –

2020年3月7日 · Also, is there any way to successfully achieve this - Create a savepoint in one transaction and rollback EVERYTHING from another transaction which was started by this first transaction? No, this is impossible. Since System.Savepoint isn't serializable, you can't actually pass it to any type of Asynchronous Apex in the first place.

2017年3月16日 · Savepoint works per transaction and you can't rollback changes across transaction. In other words, each batch execute invocation can only role its own transaction back. There is an excellent post on this here: Rollback whole Batch; You should just make an @setup method and break your 2 tests into 2 methods with 2 startTest/stopTest blocks.