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

Subscribe to my channel:

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

[froggio]

Thank you for high valuable content ;)

[ZhonghaoQian]

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.

[SupahBro]

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

[devarghyaray]

Can you make video on SSRS report on d365 please