D365 TTSBegin and TTSCommit

D365 ttsbegin and ttscommit statements in x++ mark the beginning and end of changes to data that all need to either be written or reverted. Understand where to put these, as well as how to prevent unbalanced tts errors.
#Dynamics365 #Dynamics365Musings #MSDyn365 #MSDyn365Community #DYN365O #D365FO #Microsoft #d365ug #xppgroupies #D365 #TTSBegin #TTSCommit #UnbalanceTTSBegin #TransactionBlocks
dynamics365musings.com/d365-t...
Subscribe to my channel:
/ @peterramer
Related Blog: dynamics365musings.com
LinkedIn: / peter-ramer
Twitter: / peter_ramer
00:00 - Intro
00:08 - D365 TTSBegin and TTSCommit
00:48 - Understanding transaction blocks
03:15 - Why You Need These
04:43 - Basic Example
06:36 - ForUpdate
07:18 - Update customer deep dive example
08:44 - Where to Place TTSBegin and TTSCommit
11:34 - Nested Transaction Blocks
14:47 - Unbalanced ttsBegin and TTSCommit
17:10 - TTSAbort
17:42 - Conclusion
18:29 - Outro

[@Tavakoli2012]

Thanks for this video! 🙏

[@peterramer]

My pleasure!

[@user-kd7hn8pk4z]

Thank you very much, this video is very helpful. Could you please explain why we do not need to use ttsbegin and ttscommit around update record set? I think this statement does almost the same thing as the update statement.

[@TonyTigerTonyTiger]

With "nested transactions" in SQL Server, there is only a single actual transaction, with only 1 actual begin (the first) and 1 actual commit (the last). Any intervening/nested beginnings of transactions just increment a counter (in X++ the equivalent is ttsLevel) and any intervening/nested commits of a transactions just decrement that same counter. Since there is only 1 actual transaction, nothing is committed until that 1 actual transaction ends.

[@peterramer]

Exactly! Thanks!

[@froggio]

Thank you for high valuable content ;)

[@peterramer]

Thank you for your kind words!

[@SupahBro535]

Thanks for this video! I was just wondering what the purpose and cases in which these statements are needed.

[@peterramer]

You must use them in code whenever you call the update method or delete method on a table browser. If you don’t have them, then the code will run, but no change will actually occur. After those core reasons, you may want to use them to ensure more than one record all get committed at the same time; or all rolled back if there is an error.

[@devarghyaray]

Can you make video on SSRS report on d365 please

[@SupahBro535]

I second this!

[@peterramer]

Yes. I will try to get to this soon.