Why we use ttsbegin() & ttscommit() using x++ in d365fo

 Why we use ttsbegin() & ttscommit() using x++ in d365fo

If someone is trying to deleting the same record from the Table at the same point of time, and we also doing some operation on the particular record. 

So, two operations will not do on the same point on same record that is really Deadlocking Process.

So, once the transaction has begin if any other user trying to deleting that record, that operation will be in pending mode in Queue.

Once the operation is committed with ttsbegin() and ttscommit() , the only system will allow the next operation to the next user.

So, at a time two operation will not perform on same record, so that is the reason we are locking the record temporarily. Once the operation has done, system will release the record for further operation. It is the reason always we need to write ttsbegin() & ttscommit().

For update and delete method we need to write ttsbegin() & ttscommit(). But for insertion process we don't need to write.

Enjoy 😊