# Microsoft Dynamics GP
## Overview
The **Microsoft Dynamics GP (Great Plains) Connector** enables seamless integration between **Microsoft Dynamics GP (Great Plains)** and other cloud or on-premise applications using **DBSync Cloud Workflow**. This facilitates data transfer between Dynamics GP accounting application and CRM software, e-commerce platforms, and other systems like Salesforce, SkuVault, QuickBooks, and databases.
The connector connects directly to your GP instance, allowing you to query, add, and modify 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.
## Key Benefits
**For Business Users:**
* **Accurate Financial Data:** Keep accounting and operational data aligned across systems.
* **Reduced Manual Effort:** Eliminate duplicate data entry and reconciliation tasks.
* **Improved Visibility:** Enable consistent reporting across finance and operations.
**For IT & Integration Teams:**
* **Hybrid Integration Support:** Connect on-premise Dynamics GP with cloud applications.
* **Secure Data Exchange:** Uses authenticated connections and encrypted communication.
* **Flexible Automation:** Supports scheduled, event-driven, and on-demand workflows.
## Uses
The DBSync GP connector can automate processes in real-time between MS Dynamics GP and other applications. It can be used to:
* Synchronize customer master databases with MS 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.
## Prerequisites
Before configuring the connector, ensure the following:
1. **DBSync Cloud Workflow Account**
* A valid license for this connector and access to the DBSync Cloud Workflow platform.
2. **Access to Dynamics GP**
* Valid license to access Dynamics GP and its database
3. **eConnect Installation (Required only when querying objects from Dynamics GP)**
* 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.
4. **Remote Agent** (Required only when querying objects from database)
* Installed for secure connectivity to on-premise systems.
## Connector Configuration
Each connector instance represents a single Dynamics GP company database. For multiple connections (e.g., sandbox and production), create independent connection instances for each.
## Quick Setup Guide
{% stepper %}
{% step %}
### Login to DBSync Cloud Workflow
Use your DBSync credentials to access the platform.
{% endstep %}
{% step %}
### Add the Salesforce Connector
Navigate to the connectors list in the Apps pane and select Great Plains.
{% endstep %}
{% step %}
### Enter configuration details
* **eConnect Port:** Use the eConnect port to connect to eConnect services. The default is 18888
* **Datasource**: The instance name where eConnect is installed.
* **Database Name**: The company-specific database to connect to. Find the database name in GP UI: Microsoft Dynamics GP → Maintenance → SQL.
* **Remote Agent:** Select the required Remote Agent from the dropdown.
{% endstep %}
{% step %}
### Test the connection
{% endstep %}
{% step %}
### Save the connector configuration
{% endstep %}
{% endstepper %}
Once configured, GP entities become available for workflow design.
## Common Integration Scenarios
* **Finance System Integration**
* Sync customers, invoices, and payments with CRM or accounting platforms.
* **ERP to CRM Synchronization**
* Keep customer and transaction data aligned across systems.
* **Data Warehousing**
* Replicate GP data to analytics and BI platforms.
* **Order & Inventory Automation**
* Integrate GP with eCommerce and fulfillment systems.
## FAQs
Is Dynamics GP supported as an on-premise system?
Yes, the connector supports on-premise Dynamics GP environments.
Can I sync data bi-directionally?
Yes, workflows can be configured for one-way or bi-directional data synchronization.
Is the DBSync Agent required?
It may be required depending on network and deployment architecture.
How is security handled?
All connections are authenticated and data is encrypted during transmission.
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:
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.`
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.
## Best Practices
* Use a **dedicated GP user** for integrations
* Separate **test and production** connector instances
* Schedule large sync jobs during off-peak hours
* Monitor workflows for errors and retries
## Summary
The **Microsoft Dynamics GP Connector** provides a reliable and secure way to integrate on-premise ERP data using DBSync Cloud Workflow. By automating data synchronization, organizations can improve accuracy, reduce manual effort, and enable seamless integration across business systems.
## Useful Links
[eConnect Documentation](http://msdn2.microsoft.com/en-us/dynamics/gp/bb457189.aspx)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.mydbsync.com/cloud-workflow/2026_connectors_new/microsoft-dynamics-gp.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
