Microsoft Dynamics GP Connector

Learn how to use Microsoft Dynamics GP connector in DBSync Cloud Workflow

Overview

DBSync's Dynamics GP connector enables seamless integration between Microsoft Dynamics GP (formerly Microsoft Great Plains) and other applications, such as CRM software, e-commerce platforms, and other systems. This connector facilitates data transfer between Dynamics GP and applications like Salesforce, SkuVault, QuickBooks, and databases.

With the DBSync GP connector, you can efficiently move data in and out of the Microsoft Dynamics GP Accounting application. The connector connects directly to your GP instance, allowing you to query, add, modify, and delete records such as Accounts, Customers, Sales Orders (SOP), Invoices, and more.

The DBSync GP connector extends the eConnect interface from Microsoft Dynamics GP to exchange data with the GP database. eConnect is a Microsoft programmatic interface layer that ensures data integrity by performing business validations. It is implemented as a set of database stored procedures installed on the GP database server. eConnect must be installed before using the DBSync GP connector.

Prerequisites

To establish a connection to GP using the DBSync GP connector, you must:

1. Have a valid license for the DBSync GP connector and login credentials (username and password) to connect to the DBSync iPaaS platform.

2. Have access to Dynamics GP and its database.

3. Have eConnect installed on the same server as GP to connect to its database. Refer to the Microsoft documentation for eConnect libraries for installation and configuration details.

Connector Configuration

A GP connector instance represents a single GP account with specific login credentials. If you need to connect to multiple GP instances (sandbox or production), create a separate connection for each. The table below outlines the parameters required to open a connection to a GP user instance:

Property	Description	Required
eConnect Port	Use the eConnect port to connect to eConnect services. The default is 18888.	Yes
Datasource	The instance name where eConnect is installed.	Yes
Database Name	The company-specific database to connect to. Find the database name in GP UI: Microsoft Dynamics GP → Maintenance → SQL.	Yes

After creating a connector within a project, configure it accordingly. DBSync can then map to and from the systems supported by our standard connector list and use the GP connector to retrieve data from or send data to the GP platform.

Click here to learn about all supported connectors.

Uses of MS Dynamics GP Connector

The DBSync GP connector can automate processes in near real-time between MS Dynamics GP and other applications. It can be used to:

• Synchronize customer master databases with Microsoft Dynamics GP.

• Convert opportunities won to orders generated in MS Dynamics GP.

• Convert opportunities won to invoices in MS Dynamics GP.

• Integrate e-commerce website orders with MS Dynamics GP.

• Reconcile payments received from online payment systems.

Supported Versions

DBSync's GP connector supports the following GP versions:

• Microsoft Dynamics GP 9.x

• Microsoft Dynamics GP 10.x

• Microsoft Dynamics GP 2010.x (11)

• Microsoft Dynamics GP 2013.x

Frequently Asked Questions

Frequently Asked Questions (FAQ)

What is the prerequisite software requirement for DBSync integration with Microsoft Dynamics GP? The eConnect libraries must be installed, but the full eConnect runtime module is not required.

Does DBSync need to be installed on the same machine as Microsoft Dynamics GP? The DBSync Microsoft Dynamics GP connector can be configured either on the same instance where GP is installed or on a remote machine that can access the GP database. It requires DBSync Remote agent configuration.

What are the limitations of DBSync integration with Microsoft Dynamics GP? The eConnect interfaces do not support every object and interaction within Microsoft Dynamics GP. For integrations requiring objects from other modules or sophisticated queries, use our Database connector for Microsoft SQL Server to connect directly to backend database tables. However, direct access to the GP database is generally not recommended to maintain data integrity and business rule execution.

Why is the Microsoft Dynamics GP Connector not getting validated in DBSync? If the GP connector does not validate, the eConnect service may be unable to start. To ensure eConnect service availability:

1. Locate the eConnect web services configuration file, typically at: C:\Program Files\Microsoft Dynamics\eConnect 11.0\Service\ Microsoft.Dynamics.GP.eConnect.Service.exe.config.

2. Open this file with a text or XML editor and change the httpGetEnabled parameter to false.

Can I connect multiple GP instances with a single DBSync connector? No, each GP instance requires a separate connector configuration to ensure data integrity and proper mapping of records between systems.

How frequently can data be synchronized between Dynamics GP and other systems? Data synchronization frequency can be configured based on business requirements, ranging from real-time updates to scheduled batch processes.

Does the GP connector require the remote agent to be configured? Yes, after configuring the GP connector, you need to install the DBSync remote agent on the same machine where GP is installed. The remote agent should be set up as a Windows service to facilitate seamless communication between DBSync and Microsoft Dynamics GP.

Useful Links

1. eConnect Documentation