https://stefanmaron.com/tags/interfaces/Recent content in Interfaces on Stefan Maron | Business Central & AL DevelopmentHugo -- gohugo.ioMon, 14 Oct 2024 09:00:00 +0100https://stefanmaron.com/posts/interfaces-in-business-central/Mon, 14 Oct 2024 09:00:00 +0100https://stefanmaron.com/posts/interfaces-in-business-central/Interfaces still cause a fair amount of confusion, even among developers who have been writing AL for a while. I wanted to do a proper walkthrough — from the basics to real-world patterns like testing with fake implementations and the enum+interface combination that I use most often in practice. You can watch the full stream on YouTube if you want to follow along. The basic idea The classic vehicle example works well here.https://stefanmaron.com/posts/msdyn365bc-ntfy-development-session/Tue, 16 Jul 2024 09:00:00 +0100https://stefanmaron.com/posts/msdyn365bc-ntfy-development-session/Push notifications from Business Central to your phone — that’s the idea behind MSDyn365BC.Ntfy . In this stream session I worked on rethinking the data model for the app, which started as a proof of concept and needed some structural improvements before it was worth building on further. The full stream is on YouTube if you want to watch it live. Below I’m covering the key decisions and code changes from that session.https://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.https://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 .https://stefanmaron.com/posts/al-automatic-write-offs-overpayments-interface-pattern/Sat, 25 May 2024 09:00:00 +0100https://stefanmaron.com/posts/al-automatic-write-offs-overpayments-interface-pattern/This stream picked up mid-session on an app I’m building for AppSource: an automatic write-off tool that generates general journal lines for small remaining amounts on customer ledger entries. The previous stream had a frozen screen issue — VS Code appeared fine in my preview but wasn’t actually updating — so I restarted and recapped quickly before jumping back in. The full stream is on YouTube if you want to follow along.https://stefanmaron.com/posts/be-careful-with-dynamic-code/Wed, 11 Aug 2021 07:09:13 +0000https://stefanmaron.com/posts/be-careful-with-dynamic-code/I believe there is a time in every AL developers live where he discovers the power of RecordRef and FieldRef. It is surely Incredible what you can achieve with these tools and how fast you can deliver a pretty good working piece of code. At least this is the way I remember my first solutions I build when I first learned about RecordRefs. I realized, the more I think about it the more code could be written with a dynamic approach and I started to deliver my finished code quite a bit faster.