Error Handling on Stefan Maron | Business Central & AL Developmenthttps://stefanmaron.com/tags/error-handling/Recent content in Error Handling on Stefan Maron | Business Central & AL DevelopmentHugo -- gohugo.ioWed, 10 Jul 2024 09:00:00 +0100BCv24 Error Info Wrapper - Backporting the Fluent ErrorInfo APIhttps://stefanmaron.com/posts/bcv24-error-info-wrapper/Wed, 10 Jul 2024 09:00:00 +0100https://stefanmaron.com/posts/bcv24-error-info-wrapper/On a recent stream I built a fluent wrapper around the ErrorInfo data type that lets you chain calls like ErrorInfoWrapper.Title('...').Message('...').AddAction(...). The original implementation used the this keyword, which is only available from AL runtime 14.0 (Business Central v25) onwards. Someone in the chat — I think it was Natalie — pointed out that it would only work on v25+. I was pretty sure we could make it work on v24 too, so that’s what this stream was about.Creating the ErrorInfo Wrapperhttps://stefanmaron.com/posts/creating-the-errorinfo-wrapper/Fri, 05 Jul 2024 09:00:00 +0100https://stefanmaron.com/posts/creating-the-errorinfo-wrapper/In this stream I built something I’ve been meaning to do for a while: a wrapper codeunit around the ErrorInfo type in AL. If you’ve ever tried to use ErrorInfo properly — with custom dimensions, navigation actions, fix-it actions — you know how much boilerplate it takes. I wanted to fix that. The full stream is on YouTube if you want to follow along. The repo is at github.com/StefanMaron/ErrorInfoWrapper .Build a better way to catch errors 2 – without the test frameworkhttps://stefanmaron.com/posts/build-better-error-catching-without-test-framework/Thu, 30 May 2024 09:00:00 +0100https://stefanmaron.com/posts/build-better-error-catching-without-test-framework/In the first stream on this topic I built a way to reliably catch and log errors during Business Central imports using the test framework — running code inside a test codeunit so that any database changes roll back automatically when an error is thrown. The idea worked. But then I tried to run it in production Online, and it blew up immediately: the test framework is not available in production SaaS tenants.Build a better way to catch errors (Part 1) - The BC Coding Streamhttps://stefanmaron.com/posts/build-better-error-catching-part-1/Tue, 28 May 2024 09:00:00 +0100https://stefanmaron.com/posts/build-better-error-catching-part-1/This stream started as a debugging session. I’d hit a problem in a real project: I needed to catch errors from field validations — including all the hidden commits that Validate can trigger — without leaving any trace in the database. I wanted to show the user what would go wrong before actually doing the thing. Turns out that’s harder than it sounds. You can watch the full stream on YouTube .