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.
Tag Archives: Debug
Business Central, fast debugging with AL Object Designer
Debugging can be done in different ways, I want to report only how to do it with AL Object Designer. This great extension is always evolving, a must for every installation of VS Code and Microsoft AL.
With AL Object Designer, it is possible to manage all Business Central objects, both manually and through the Generation Wizard.
Debug without publishing
Recently, with the Developer Preview – February 2019, a new feature was added to the AL extension for Visual Studio Code: Debug without publishing. This new feature brings more than you would expect. It is not just another option in the list of Publish and Publish without debugging.
Source : Kauffmann @ Dynamics 365 Business Central
Read more…
Debugging with SQL Profiler
One additional tool that you can use to debug Nav is the SQL Profiler. This comes with most SQL installations. With it you can see all the SQL commands that Nav runs. The only issue with using it right away is that you get a lot of commands that done mean a whole lot.
Debugging Workflows with Step IDs
Getting a Little Complex? If you have been messing around with making workflows, you know it can sometimes get a little messy. This happens a lot when you start moving your steps and responses around.
Impossible to debug the Job Queue in NAV 2016?
I guess I am not the only one that has installed NAV 2016 running the Job Queue. If the Job Queue is running a job that causes error you are likely to start the debugger on the service tier running the Job Queue and start with a Debug Next.
How To: Debug a Webservice/NAS Session in NAV 2013/NAV2015 and above
Finally! How many hours have I spent debugging sessions without UI with MESSAGEs and ERRORs… The good old days.
If you have done that, like me, then you will probably agree that it was not the most elegant way of finding the source of the problem. Have you ever forgotten to delete a funny MESSAGE after a session debugging with that method and had the client bring it up? I know I have.