General Information

Microsoft Dynamics GP® eConnect Enterprise Application Integration (EAI) offers fast and accurate access to an extensive set of Microsoft Dynamics GP back office document transactions. Businesses deploying the eConnect programmable document integration package receive an easy-to-use and customizable set of tools. The programmable document integration* package permits outside data sources, such as Web storefronts, earlier applications, and point-of-sale systems, to easily create back office transactions and send back office requests to view specific documents and document lists. The use of eConnect enables development teams to focus on custom application development in the data source with the ability to snap in eConnect for valuable back office transactional access.

Microsoft Dynamics GP eConnect EAI, deployed in conjunction with existing Web storefronts or other data sources, enables Web integrators to provide cost-effective solutions while reducing the cost of recoding for new environments. eConnect also provides the ability to use the transaction-based business logic in Microsoft Dynamics GP. Users can extend that business logic without rewriting existing functionality. Business utilization is endless, including the ability to provide document access for service-oriented front office custom applications, quick connectivity from existing data sources to Microsoft Dynamics GP, and a simple, cost-effective method of connecting to existing storefront and service applications.

eConnect uses the power of Microsoft® SQL Server™ to house all of the back office business logic. The eConnect sample connectivity tools enable developers to choose from a variety of industry-standard programming tools to connect applications to the back office accounting system.

These eConnect tools include:

  • Microsoft Windows® EAI Service (built on the Microsoft .NET Framework), which is a transport mechanism for delivering and/or retrieving Message Queuing (also known as MSMQ) messages from the back office
  • The transaction schemas and XML examples that can be used with all of the eConnect connectivity tools
  • A Microsoft BizTalk®** Adapter that can be used to quickly snap eConnect into your existing BizTalk Server implementation
  • A Microsoft Visual Basic® COM object that can be used independently or in conjunction with other eConnect tools to access back office transactions.

Note Throughout the Help documentation, the terms front office and back office are used. In a distributed environment, front office refers to the customer relationship management system, data warehouse, Web site, or other application that communicates with the back office. The term back office refers to your financial management system. In the eConnect environment, the back office consists of Microsoft Dynamics GP running on a SQL Server–based server.

* Existing transaction update functionality is not all-inclusive. Refer to the All XML Nodes Used in eConnect Schemas list for reference to which nodes currently have update functionality.

** BizTalk is not required to use eConnect.

***A Functional Currency setup is required with eConnect. eConnect requires a currency ID set up even if working with a non-Multicurrency company. Find more information in Troubleshooting.