TRY..CATCH

In my two last posts, I laid out the technical design of the Preview Posting feature, and then showed how to simplify its design to get around the unwanted behavior of TryFunction . One thing is obvious from these posts: Preview Posting wants to simulate posting of a document (or journal) to show what the results would be, but without leaving any actual trace in the database.

If this was a joke, then it would be one of those good-news-bad-news jokes. So which one do you want first? To stay true to all jokes of this kind, I’ll start with good news first. Good news is, you now have TryFunction s, that return true if no error happens, and false if an error happens inside them.

While it may be a cold day in hell before we see any TRY..CATCH constructs in pure C/AL, we are all far more lucky when it comes to .NET interoperability. In this blog post I’ll (re)present the same concept I demonstrated during NAV TechDays 2013 last year in Antwerp, because I am quite sure this nifty little trick got lost under piles of other posts on this blog.

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?