Skip to main content

Debugging in Nav 2009 R2 and Earlier Version of Classic Client.


Hi all,

As most of us know that due to changes in version there has been changes in Debugging Process of Navision Processes.
Let's start with the Orignal Debugging version of Navision i.e Debugging in classic client.

In classic client the debugger was present in the classic client window itself under Tools Sections.

Here are some screenshot of the debugger in classic client -





As you can see in the image above, under Tools - Debugger we find two options - Active and BreakPoint on Trigger.

Active - Activates the Trigger.
Breakpoint on tigger - Break the Process and switch to Debugging Mode (works only if Debugger is active).

If Debuggers is set to active and Breakpoint on trigger is set to inactive it breaks at the point where error occurs in the process.

But If debugger is set to active and Breakpoint on trigger is also set to active it breaks the process as soon as we start the process.


Let's try to post a sales order where status are - Debugger set to active and Breakpoint on trigger is set to inactive.



As you can see the debugger windows gets opened because i didnt specified external document No.
The debugger stoped at the exact code line where error occurred.

But at the same time see the Variables highlighted in the image, the variables are uninatlized which are not currently in use. These variables values get lost as they are not in use.

On the other hand if i set Debugger to active and Breakpoint on trigger to active, it will keep all variables active but it will take lot of time to reach the error point.


This post only contain details of classic Debugger, in the next post i will explain the Debugging Process in Navision 2009, 2009 SP1 and 2009 R2 RTC Client.


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

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.