Dynamics Community Forum Thread Details

What is the purpose of the eConnect tables?

What is the purpose of each of these eConnect tables?

eConnect_Out

eConnect_Out_Setup

eConnectOutTemp

I am curious because I just delivered an eConnect routine which works in our developer environment but does nothing in production.

There are no errors produced just simply no records written to the GP database.

Categories:

Microsoft Dynamics GP

Hi Richard,

These are mostly used for Requester for eConnect. Here is a general summary of these tables, but there is more informaiton in the eConnectProgrammersGuide.PDF file that's in the Help folder of your eConnect Install.

eConnect_Out This table stores data from selected create, update, or delete operations that occur within Microsoft Dynamics GP. The data identifies the individual transactions that occurred. The Outgoing Service uses the data in this table to create an XML document that is placed in a queue.
eConnect_Out_Setup This table contains configuration information for the Transaction Requester. To keep the Transaction Requester working, do not make changes to this table.
eConnectOutTemp This table is a temporary data store.

Being that eConnect is SQL based for pushing the data into your database, you should be able to identify why your integration is not processing in production by running a SQL trace during the process.

I would run the Trace with our recommended parameters selected for Microsoft Dynamics GP Troubleshooting to make sure any error messages would be visible. If nothing shows up on the trace, then you will have to make sure that whatever UI you are using to connect to the eConnect Service is set up properly and pointed to your right SQL instance in live.

How to use SQL Profiler to create an SQL trace in Microsoft SQL Server

http://support.microsoft.com/help/912281

Thanks,

Isaac Olson

Microsoft Support

Quick Links

Leaderboard