A few weeks back, I watched Erik Hougaard‘s youtube video “Make your own Date Filters in AL and Business Central” and thought of trying it and adding my own bit to it.
First, what was the intention with custom filter tokens?
The standard application comes already with some tokens.
It’s that time of the year again, Microsoft has released a new version of Business Central and I fire up the old decompiler and check what’s new under the hood of the AL compiler.
After the “What’s New” webcast I’ve done two days ago, I’ve received questions on some new features introduced with Dynamics 365 Business Central 2021 Wave 2 (version 19) that (due to lack of time) I’ve presented quickly.
One of these features was the new way of raising errors that you can use with version 19, alias the Collectible errors.
In my previous post I discussed how you could use your .dlls in an On Prem enviroment hosted on your local machine for those who hasn´t jumped to the cloud yet. https://businesscentralgeek.com/how-to-use-dotnets-for-bc-on-premise
In this post I will show you how to do it in a Docker container. The purpose is to test your extensions and .dlls in the lasts versions of Business Central before updating your production app. This is a good practice to make sure they work correctly in every minor and major update.
Not too long ago, I followed one of Steve Endow’s amazing livestreams where he was talking about BC Coding Guidelines together with Henrik and Jeremy. And what I noticed was that it appeared to be that “coding guidelines” – whatever they are for you – are hard to find – at least if you’re searching for guidelines in the new AL Language.
In June 2021, I discussed my circuitous journey to learn about and understand the $metadata and $expand OData “query options” and how to use them with the Business Central web API.
In this video, I take a look at how to use the var prefix for passing parameters to procedures. I look at common mistakes and some gotchas that you might not be aware of.