Extending the Default eConnect Business Logic with 'Pre' and 'Post' Stored Procedures

This is fourth 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 APIs within Visual Studio. Part 3 examined using eConnect directly from a SQL stored procedure


Requires FREE Membership to View

Become a Member Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also receive periodic email newsletters with the latest relevant articles and content updates.
About Gloria Braunschweig

Gloria has experience across the full spectrum of business operations and management. Decades of experience are documented in the book Rapid Implementation, establishing Gloria as a specialists using Microsoft SQL tools for implementation, integration, and business intelligence related to Microsoft Dynamics GP.

Gloria writes and presents on lean implementation concepts and business management systems for small and mid-size businesses. 

Read full bio...

About W. Mike Harris

Mike brings strong data integration and conversion skills to Computeration.  His "can do" attitude gets data integrated into new systems quickly and cleanly.  He has delved into multiple legacy accounting products to retrieve data, utilizing Microsoft Access, Excel, Visual Basic, and SQL tools to convert and integrate data.

Mike utilizes his technical skills to develop efficient and economical customizations for clients.  He works with SharePoint, Business Portal, Web Services, SQL Reporting Services, and other legacy databases and reporting technologies. 

Mike's goal is to aid clients in their day-to-day processes.  His proficiency with the tables and fields in Dynamics, along with the process flows within all the modules, facilitates his ability to quickly and efficiently complete the migration of data.

Read full bio...

Caveats to Pre and Post stored procs

Thanks for the article.

Two caveats about using the eConnect Pre and Post stored procedures.

1. The Pre and Post stored procedure parameters can vary between Dynamics GP minor versions. So if you develop and test the proc on GP 2010 SP 3, it may cause errors if deployed in a GP 2010 SP 1 environment due to a different number of parameters. The safest way to deploy is to script the Pre or Post procedure from the client's server first, and then copy your procedure code into that script.

2. Related to the above, the Pre and Post stored procedures are removed and recreated during GP upgrades. So make sure to have backups of the procedure scripts, and after an upgrade, review all of the parameters of the new procedure, comparing them to the old procedure, before re-deploying the procs. Invariably, this is forgotten, the custom pre and post scripts are removed, and clients wonder why certain eConnect data have problems after an upgrade.


Steve Endow
Dynamics GP Certified Trainer
Dynamics GP Certified IT Professional


Good reminders, Steve. Thank you for contributing.

Gloria J. Braunschweig, CMA
President, Computeration, Inc.