How to use the Dexterity Script Debugger to trace bugs and issues in Microsoft Dynamics GP

Dexterity Script Debugger

We can use the Dexterity Script Debugger to trace bugs and performance issues in Microsoft Dynamics GP.

The script debugger is accessed from the Debug menu, which is available in both tools mode and test mode. The following is a list of the debugger-related items in the Debug menu.

But in the live environment this option not available by default and to make enable the Dexterity Script Debugger option in live follow these steps:

1.	Change the Dex.ini file by adding the following lines to the [General] section. ScriptDebugger=TRUE ScriptDebuggerProduct=0 Note:The product ID is typically set to zero for Microsoft Business Solutions - Great Plains, but the product ID can be the product ID of any product in the Dynamics.set file.
2.	Start Microsoft Dynamics GP or Microsoft Business Solutions - Great Plains, and then log on to the application.
3.	In the application, move to a location just before the section of code that you want to analyze.
4.	To analyze the code, follow these steps: a. Click Debug, click Log Scripts, and then specify a path for the Script.log file. b. Click Debug, and then click Profile Scripts. c. Click Debug, and then click Clear Profile.
5.	Perform the action that you want to analyze.
6.	To stop the analysis, follow these steps: a. Click Debug, and then click Log Scripts. b. Click Debug, click Save Profile, and then specify a path for the Profile.txt file. c. Click Debug, and then click Profile Scripts.
7.	Locate the Script.log file and the Profile.txt file, and then send these files to a developer or to the support team for analysis.

The Dexterity Script Debugger uses two methods to trace what is occurring in the code:

1-Script Profiler

The Script Profiler lets you analyze script and table activity during test mode, allowing you to optimize your scripts and streamline your application. Once you’ve started the profiler, it records the name of every script run and how much time is spent running each script. The Script Profiler also tracks how many times tables were accessed and the average and total times for specific operations on each table accessed. The time required by the profiler itself is automatically deducted from the profile, so that the profile shows the time requirements for only your application, for more information refer to dexterity help.

2-Script Logger

The script logger stores a record of all the attached scripts, procedures, user-defined functions, and function library functions that were run while your application was being executed in test mode. It also lists any parameters passed to the procedures or functions that were called. for more information refer to dexterity help.