Transactions
-
How about Rollback in AL?
I’ve never truly understood why we could explicitly commit a transaction, but we could only implicitly roll one back. There is a universe of difference between throwing an error (and ending the call stack), and rolling back (and continuing execution). There was always a way to roll back and go on, sure.
-
Out-of-transaction database writes
Ancient wisdom goes that you cannot have more than one write transaction going on at the same time in a single session in NAV. This is absolutely true, in and out. Some features, like Activity Log , will leave you wanting to be able to write to the database outside of the normally running transaction.
-
Activity Log or Activity Lock pattern?
Today at NAV TechDays 2015 in Antwerp, I attended a presentation by Nikola Kukrika, Ciprian Iordache, and Gary Winter, at which Ciprian presented a new design pattern based on a new feature in NAV 2016: Activity Log.
-
TRY.. CATCH in C/AL
Did I CATCH your attention yet? At least I did TRY. Now that I have completed my series on exception handling in C/AL , a very valid question pops up: why don’t we have try..catch syntactical constructs in C/AL, the way we have it in other programming languages?