Sunday, August 26, 2012

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.

Saurav Dhyani

No comments:

Post a Comment

Popular Posts