Activity Forums Salesforce Questions and Answers Limitations of using a Savepoint in apex

  • Limitations of using a Savepoint in apex

  • Anjali

    Member
    September 14, 2018 at 1:09 pm

    What are the limitations of using a Savepoint in apex?

  • Avnish Yadav

    Member
    September 14, 2018 at 1:16 pm

    Hello,

    Limitations of using a Savepoint are :-

    • If you set more than one savepoint, then roll back to a savepoint that is not the last savepoint you generated, the later savepoint variables become invalid.

    • Each savepoint you set counts against the governor limit for DML statements.
    • Static variables are not reverted during a rollback. If you try to run the trigger again, the static variables retain the values from the first run.
    • Each rollback counts against the governor limit for DML statements. You will receive a runtime error if you try to rollback the database additional times.
    • The ID on an sObject inserted after setting a savepoint is not cleared after a rollback.

    Thanks.

  • madhulika shah

    Member
    September 14, 2018 at 1:18 pm

    Hi Anjali,

    Limitations of using Savepoint in apex are:

    • If you set more than one savepoint, then roll back to a savepoint that is not the last savepoint you generated, the later savepoint variables become invalid. For example, if you generated savepoint SP1 first, savepoint SP2 after that, and then you rolled back to SP1, the variable SP2 would no longer be valid. You will receive a runtime error if you try to use it.
    • References to savepoints cannot cross trigger invocations because each trigger invocation is a new trigger context. If you declare a savepoint as a static variable then try to use it across trigger contexts, you will receive a run-time error.
    • Each savepoint you set counts against the governor limit for DML statements.
    • Static variables are not reverted during a rollback. If you try to run the trigger again, the static variables retain the values from the first run.
    • Each rollback counts against the governor limit for DML statements. You will receive a runtime error if you try to rollback the database additional times.
    • The ID on an sObject inserted after setting a savepoint is not cleared after a rollback. Create an sObject to insert after a rollback. Attempting to insert the sObject using the variable created before the rollback fails because the sObject variable has an ID. Updating or upserting the sObject using the same variable also fails because the sObject is not in the database and, thus, cannot be updated.
  • Parul

    Member
    September 14, 2018 at 1:35 pm

    Hi,

    Below some limitations are mentioned :

    Each savepoint you set counts against the Governor limit for DML statements.
    If you insert the ID on an SObject after setting the savepoint, the ID will not be cleared after a rollback.
    Static variables are not reverted during a rollback. If you run the trigger again, the static variables will retain the values from the previous run.

     

    Thanks.

  • Prachi

    Member
    September 14, 2018 at 1:54 pm

    hi,

    The limitations of Savepoint or Transaction Control in Apex are:

    1. Each savepoint you set counts against the governor limit for DML statements.
    2. Static variables are not reverted during a rollback. If you try to run the trigger again, the static variables retain the values from the first run.
    3. Each rollback counts against the governor limit for DML statements. You will receive a Runtime error if you try to rollback the database additional times.
    4. The ID on an sObject inserted after setting a savepoint is not cleared after a rollback.

    Thanks

  • shariq

    Member
    September 14, 2018 at 9:47 pm

    Hi,

    All requests are delimited by the trigger, class method, Web Service, Visualforce page or anonymous block that executes the Apex code. If the entire request completes successfully, all changes are committed to the database. For example, suppose a Visualforce page called an Apex controller, which in turn called an additional Apex class. Only when all the Apex code has finished running and the Visualforce page has finished running, are the changes committed to the database. If the request does not complete successfully, all database changes are rolled back.

    Sometimes during the processing of records, your business rules require that partial work (already executed DML statements) be “rolled back” so that the processing can continue in another direction. 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.

    The following limitations apply to generating savepoint variables and rolling back the database:

    • If you set more than one savepoint, then roll back to a savepoint that is not the last savepoint you generated, the later savepoint variables become invalid. For example, if you generated savepoint SP1 first, savepoint SP2 after that, and then you rolled back to SP1, the variable SP2 would no longer be valid. You will receive a runtime error if you try to use it.
    • References to savepoints cannot cross trigger invocations because each trigger invocation is a new trigger context. If you declare a savepoint as a static variable then try to use it across trigger contexts, you will receive a run-time error.
    • Each savepoint you set counts against the governor limit for DML statements.
    • Static variables are not reverted during a rollback. If you try to run the trigger again, the static variables retain the values from the first run.
    • Each rollback counts against the governor limit for DML statements. You will receive a runtime error if you try to rollback the database additional times.
    • The ID on an sObject inserted after setting a savepoint is not cleared after a rollback. Create an sObject to insert after a rollback. Attempting to insert the sObject using the variable created before the rollback fails because the sObject variable has an ID. Updating or upserting the sObject using the same variable also fails because the sObject is not in the database and, thus, cannot be updated.

    Example -

    Account a = new Account(Name = 'xxx'); insert a;
    System.assertEquals(null, [SELECT AccountNumber FROM Account WHERE Id = :a.Id].
    AccountNumber);

    // Create a savepoint while AccountNumber is null
    Savepoint sp = Database.setSavepoint();

    // Change the account number
    a.AccountNumber = '123';
    update a;
    System.assertEquals('123', [SELECT AccountNumber FROM Account WHERE Id = :a.Id].
    AccountNumber);

    // Rollback to the previous null value
    Database.rollback(sp);
    System.assertEquals(null, [SELECT AccountNumber FROM Account WHERE Id = :a.Id].
    AccountNumber);

    Hope this helps.

  • chanchal kumar

    Member
    September 17, 2018 at 10:43 am

    Hi,

    Sometimes during the processing of records, your business rules require that partial work (already executed DML statements) be “rolled back” so that the processing can continue in another direction. 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.

  • Prachi

    Member
    September 18, 2018 at 1:20 pm

    hi,

    Hi Anjali,

    Limitations of using Savepoint in apex are:

    If you set more than one savepoint, then roll back to a savepoint that is not the last savepoint you generated, the later savepoint variables become invalid. For example, if you generated savepoint SP1 first, savepoint SP2 after that, and then you rolled back to SP1, the variable SP2 would no longer be valid. You will receive a runtime error if you try to use it.
    References to savepoints cannot cross trigger invocations because each trigger invocation is a new trigger context. If you declare a savepoint as a static variable then try to use it across trigger contexts, you will receive a run-time error.
    Each savepoint you set counts against the governor limit for DML statements.

    thanks

Viewing 1 - 8 of 8 posts

Log in to reply.

Original Post
0 of 0 posts June 2018
Now