Full Rollback in Batch Posting

Answers

• Developer101 Member Posts: 569

  2024-12-30

  I have seen it on Dynamics 365 Community Forum as well. So have you found a solution for it?

  United Kingdom

  0
• navuser1 Member Posts: 1,334

  2024-12-31

  So far, I have not found any solution.

  Now or Never

  0
• JJMc Member Posts: 63

  2024-12-31

  When you call to the posting codeunit to achieve this, you have then posibility of passing a "SuppressCommit" parameter to avoid commit for each recor you pass, and commited at the end.
  
  This way if any error occurs during the hole process, the rollback do not create, modify, delete, any registers in the database

  1
• navuser1 Member Posts: 1,334

  2024-12-31 edited 2024-12-31

  Exactly the same approach I have already implemented.
  
  
  

  Now or Never

  0
• Developer101 Member Posts: 569

  2025-01-10

  > @navuser1 said:
  > Exactly the same approach I have already implemented.
  Has this worked?

  United Kingdom

  0
• txeriff Member Posts: 515

  2025-01-13

  By Standard the posting routine will commit, I didn't know MS introduced SetSupressCommit function, in the old days we used a blank error to prevent the commit in the code (Error(''))
  
  My understanding is you have some piece of code (bespoke) that fails sometimes but the document has already been posted. I would review if you have your piece of code in the right place as it should happen before any commits, it would rollback by default.
  

  0
• vaprog Member Posts: 1,158

  2025-01-14

  SetSupressCommit only supresses any explicit call to Commit during the execution of the Codeunit. This allows you to include more database changes into the same transaction such as updating bookkeeping daten related to some interface to an external system. As such it is very different from Error('')

  1
• navuser1 Member Posts: 1,334

  2025-01-21

  @Developer101
  It seems working fine

  Now or Never

  0