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.
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.
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.
Thank you for high valuable content ;)
Thank you for your kind words!
Thanks for this video! I was just wondering what the purpose and cases in which these statements are needed.
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.
Thanks for this video! 🙏
My pleasure!
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.
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.
Exactly! Thanks!
Can you make video on SSRS report on d365 please
I second this!
Yes. I will try to get to this soon.