Combining Source Files Using Integration Manager for Dynamics GP

When using the Integration Manager, you may need to combine several files to create one source file. You can use the “Before Integration” script feature to accomplish this. To access the “Before Integration” script, double-click on the integration’s name and the integration’s “Properties” window opens. Click on the “Scripts” tab and double-click on the “Before Integration” script to reveal the Script Editor.

Example VBA script:

There are other uses for the “Before Integration” script. You can display a dialog box requiring the user to enter a password prior to starting the integration. In the example below, the user is prompted for a password, and the integration is canceled if the wrong password is supplied by the user.

After Integration Script Tip

When using the Integration Manger, you may be required to execute a stored procedure after the integration is finished. You can use the feature called the “Before Integration” script to accomplish this. To access the “Before Integration” script, double-click the integration’s name and the integration’s “Properties” window opens. Click on the “Scripts” tab and double-click on the “Before Integration” script to reveal the Script Editor.

In the example code listed below, the connection to the database is created using the ODBC Dynamics GP with the “sa” login id and password. Next, the sql stored procedure called “BKD_ABLE_Import_TradeDiscount_To_SOP_Invoice” is executed. This script will run only once at the end of the integration.

Example VBA script:

The example stored procedure listed below imports the data from a flat file to update the SOP Invoice Discount amount using the eConnect store procedure called “taSopHdrIvcInsert.”

For more information about using Integration Manager to combine files into one source files, contact BKD’s Dynamics GP Support Center.