When developing extensions for Dynamics 365 Business Central, you could have scenarios where you want to execute a procedure or a business process only if the extension is running on a SaaS environment or in an on-premise environment (or maybe having a different behaviour accordingly to the environment).
Some time ago, after explaining my most used VSCode Extensions for AL Development for (about) the 829th time – I decided to make my life a bit easier. I already came across the concept of creating a VSCode Extension that act like packages that automatically install other extensions. An “Extension Pack”, if you will ;-).
There is a recent change that I had to introduce in the CRS AL Language Extension – you know, that tiny little VSCode Extension that quite a lot of you seem to be using ;-). +89000 downloads/+21500 installs – that’s crazy! It’s one of my biggest projects I ever did for the community :-).
One of the biggest headaches right now, is the missing feature for move data from a C/AL table to an extension table without having to do export and import, RapidStart Packages or other funky operations. The idea behind my method is to avoid too much data copying and instead rely on a Rube Goldberg’sk series of SQL rename operations.
When developing an extension for Dynamics 365 Business Central (BC), one of the hardest problems is detecting which event to subscribe. To detect the event, there are two options: Go To Definition in AL code, and the Event Recorder feature. This blog discusses how to use the Event Recorder feature.
The Event Recorder is a feature that allows all the events to be listed when a certain action is performed in BC.
My last blog about my VSCode extension dates from July 2018. I have been upgrading/maintaining it meanwhile, and I am definitely not going to blog about all new small features and fixes (yes, quite necessary as well ;-)) every single time, but for this one, I really felt that an update wouldn’t hurt.