DynDeveloper.com

To modify eConnect’s business logic, place custom SQL code in the pre or post procedures. The custom code in the pre and post procedures allow you to modify or extend the behavior of the core eConnect stored procedure.

Understand that each node in your eConnect integration (taPOHdr, taPOline, taUpdateCreateItemRcd) corresponds to a stored procedure with the exact same name, and that there are two others that fire immediately before and after the integration with the same name but with 'Pre' or 'Post' appended.

So, for taPoHdr, the sequence would be:
taPoHdrPre
taPoHdr
taPoHdrPost

Got that?

To expand on that point, the various parts of an integration are (generally) integrated in the order that they're listed in the documentation. That means that the lines generally go in first. So, for a PO with two lines, you'd get this:

taPoLinePre
taPoLine
taPoLinePost
taPoLinePre
taPoLine
taPoLinePost
taPoHdrPre
taPoHdr
taPoHdrPost

To customize a pre or post stored procedure, complete the following steps:

Open the .sql file for the stored procedure.
eConnect supplies a file for each pre and post stored procedure you can modify. To find a specific file, open the folder C:\Program Files (x86)\Microsoft Dynamics\eConnect 11\Custom Procedures. Earlier versions have a slightly different path. This folder contains a subfolder for each transaction type schema. Open the subfolder that contains the stored procedure you want to modify.

As an example, assume you want to modify the taUpdateCreateCustomerRcdPost stored procedure. Open the C:\Program Files\Microsoft Dynamics\eConnect 11\Custom Procedures\Receivables folder. Next, open the taUpdateCreateCustomerRcdPost.sql file. You may edit the file using any text editor or Microsoft SQL Server Management Studio.

Add your custom SQL code.
With the .sql file open, you can add custom SQL code to the file. The only parts of the document you should change are the Revision History and the section of the file specified for custom business logic. Your SQL code should be added between the following comments:

 


To avoid errors or unexpected results, do not modify any of the other statements in the file. After adding your custom business logic, save the file.

Run the .sql file in Microsoft SQL Server Management Studio.
Open the modified file with Microsoft SQL Server Management Studio. Use the drop-down list from the toolbar to specify the Microsoft Dynamics GP database that contains the target stored procedure. Click the Execute button. The Query Messages window displays whether the stored procedure was successfully updated. If it succeeded, the stored procedure now includes your custom SQL code.

The following SQL example shows a customized taCreateTerritoryPre stored procedure. The example overrides the value in the Territory Description (SLTERDSC) parameter to reflect that the sales territory was created using eConnect:

USRDEFND

Last, note that the last 5 fields in every integration are the USRDEFND fields. These are not the same as the user defined fields that are in some tables, they are here specificaly for integration. Any value that you put in these fields is available in the Pre and Post procedures, and is then discarded. If you want to pass in some information to use, this is the place to do it.