Creating a Microsoft Dynamics GP Integration with eConnect and a SQL Stored Procedure
This is third in a series of articles covering eConnect for Microsoft Dynamics GP. Part 1 explained that the business logic for eConnect exists in stored procedures within the Dynamics GP company database. Part 2 created an eConnect integration utilizing the .NET API's within Visual Studio.
This post examines using eConnect directly from a SQL stored procedure. The stored procedures are utilized by the .NET APIs to perform business logic verifications on the data being integrated. Next, transactions that pass the verification are inserted into the appropriate transaction work tables within Dynamics GP.