Skip to main content

Debugging in NAV 2013 Client


Hi all,

As most of us know that due to changes in version there has been changes in Debugging Process of Navision Process.

Here are some screenshot of the debugger in NAV 2013 Client -

For Activating Debugger we need to Start it from Classic or Developer Environment Client Option.





This will open Session List Page, which displays all active session on that particular database.
In the image below you will find only one session because i am the only user connected to the database.



For Debugging any session, select the session from the list and click Debug. This will enable debugger.
I will open a new page as shown below.



As shown in image above the debugger is waiting for Break, on the right hand side you can see the Watch window and the Call Stack window in Factbox.

so where we are our other classic debugger options Break on Error?

Click on the Break Rules, you will find the option that we are looking for.



And guess what we have two more options - Break on Record Change ans Skip Codeunit 1.

Let's try again to Post a sales Order.

As there is no External Document Number in Sales Order we will get switched to Debugger window.



Now we are missing a only part that we had in classic client that is variables, so where is that.

Click on the variables and you will see the list.



You will find all variables values which were called before this point that is the best part of the new debugger.

If i move to another object in call stack and check the variables list i will still find all the variables in that object.



So now with this debugger we don't need to debug the whole process to see the variables. That's the best part i like about this debugger.

Enjoy Debugging :)

Regards,
Saurav Dhyani
http://saurav-nav.blogspot.com/

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.