Today I would like to talk about an interesting question I saw last week, how to debug in phone/tablet client session.
Debugging is the process of finding and correcting errors. With Visual Studio Code and the AL Language extension, you get an integrated debugger to help you inspect your code and verify that your application can run as expected.
In this video, I take a look at the new profiler in BC version 19. It’s part of the snapshot debugger, so this is almost a quick primer into snapshot debugging.
In this video, I go through the AL debugger and cover the most common features of debugging AL code. This is another video in my series AL for beginners.
Snapshot debugging allows a delegated admin to record AL code that runs on the server, and once it has run, debug the recorded snapshot in Visual Studio Code. For a delegated admin to create and download a snapshot file that exists on the server on behalf of an end-user, the delegated admin must be part of the D365 Snapshot Debug permission group.
One of the top requested features for Dynamics 365 Business Central from a long time is absolutely one: debugging the production environment! And now you can 🙂
Dynamics 365 Business Central version 17 introduces a feature called Snapshot Debugging. Snapshot Debugging allows a delegated admin to record AL code that runs on the server side and then debug the recorded snapshot in Visual Studio Code in an offline manner.
From v0.4.0 of the AL Test Runner app it is possible to debug Business Central tests without leaving Visual Studio Code. There’s a lot of scope for improvements but if you’re interested in trying it out it’s included in the marketplace version now.
This is the second part of a two-part blog series on how to set up an Extension development environment using Visual Studio code. In this article, we will continue to detail how to set up the environment in order to be able to debug an Extension.