There is always the need to interact with other systems. An ERP like
eConnect is a set of functions included in several libraries (DLLs) that are available to reference in Visual Studio.NET applications. There is a limited set of functions available in eConnect, which include: creating/updating customers, general ledger journal entries, inventory transactions, purchase orders, etc. For a full list of the supported transactions I recommend to read the Microsoft Dynamics GP eConnect Programmer’s guide and Reference. (https://msdn.microsoft.com/en-us/library/ff623839.aspx)
Here is a sample list of Dynamics GP 2013 eConnect transactions available for the Receivables module.
eConnect is a powerful tool that lets you create transactions and objects in Dynamics GP, but it has its drawbacks. One of them is that even though eConnect creates the supported transactions the same way as if a user was entering them manually in the system, eConnect has no way to detect if the system has 3rd party add-ins installed. Because of this, eConnect will not generate data for those 3rd party tables causing potential problems. In order to work around this limitation, you can take advantage of eConnect’s pre and post SQL Server stored procedures available for each eConnect transaction, to insert, update, or delete those records.
Another drawback, or at least I think is one, is that there are some properties not listed in the eConnect documentation, and that are sometimes required when creating transactions. These hidden gems can be found though when using IntelliSense within Visual Studio. Look at these two highlighted properties which are required when specifying their corresponding field values.
Yes, even though you are “specifying” a value for a field, in some cases, you have to “specify” that you are “specifying” a value for a field! So, don't be afraid to look around the IntelliSense windows, maybe you'll find the property you were looking for.
All in all, eConnect is a very useful tool that must be part of your arsenal when fighting the integrations war.
This article was written by Eduardo Sicouret, Dynamics GP Technical Consultant for
by Tridea Partners