Using the script logger

Use the Dexterity script logger to find out which procedures run during a given process. This can be a useful tool in helping you understand the call chain used for specific processes, such as posting a batch, if you don’t have source code. The following illustration shows how this utility logs scripts when calculating a document amount in the Receivables Transaction Entry window:

'RM_Sales_Entry Trade_Discount_Amount CHG on form RM_Sales_Entry'
	'RM_Sales_Entry Account_Amount CHG on form
	 RM_Sales_Entry'

	'Payment_Terms_Calculate', 498.33000, 15.00000,
	0.00000, 0.00000, 0.00000, 0, 0.00000, file
	'SY_Payment_Terms_MSTR', 0, 10/21/95, 10/21/95,
	11/20/95, 0.00000, 0.00000, 0.00000, 0.00000, 0

		'Payment_Terms_Calculate_Avail', 498.33000,
		0.00000, 0, 0.00000, 0.00000, file
		'SY_Payment_Terms_MSTR'

Not all Microsoft Dynamics GP procedures are usable within a third-party product. We recommend that, whenever possible, you use the procedures listed in Procedure list, or those recommended for use by Dexterity technical support.

Once you understand the procedures in the call chain, you can call the same procedures in your application to complete similar processing. To use the Script Logger, complete the following steps:

  1. Move to the location where the accounting system calls the procedure.

Enter Dexterity test mode and log into the sample company. Move to the window where the accounting system initiates the processing that you want to take advantage of. For instance, to find out which procedures are called when posting a single sales transaction, move to the Sales Transactions window.

  1. Create the log file.

Choose Log Scripts from the Debug menu. A dialog box will appear, allowing you to enter the name and location of the script log. The script logger will log all scripts until you turn it off.

  1. Review the script log.

View the script log using a text editor. The script log will show the procedures called and the parameters passed to each.

Documentation Feedback