Manual data entry and reconciliation, often time-consuming , expensive , error-prone and often the result of disconnected systems with duplicated efforts in managing customer information, invoices or getting payments something that is not easily shared and updated.
DBSync allows you to integrate your front- and back-office applications to streamline and automate your business processes and ensure that your Microsoft Dynamics GP (Great Plains) data is accurate, timely, and functional.
DBSync can automated in near real-time between Microsoft Dynamics GP and other applications and can be used to
- Synchronize Customer Master Databases with Microsoft Dynamics GP
- Convert Opportunities Won to Order generated in Microsoft Dynamics GP
- Convert Opportunities Won to Invoice in Microsoft Dynamics GP
- Integrate E-commerce website orders to Microsoft Dynamics GP
- Integrated payments received from online payment systems for reconciliation
Frequently Asked Questions
What are the supported versions of Microsoft Dynamics GP (Great Plains)?
- Great Plains 9.x
- Great Plains 10.x
What are the pre-requisite software requirement for DBSync integration with Microsoft Dynamics GP?
The eConnect libraries must be installed (eConnect Documentation) however the full eConnect Runtime module does not need to be installed.
Does Dbsync need to be installed on the same machine as that of Microsoft Dynamcs GP?
DBSync Microsoft Dynamics GP (Great Plains) adapter can be either configured on the same instance GP is installed or on a remote machine which can access Great Plains database.
What are the limitations of DBSync integration with Microsoft Dynamics GP?
The eConnect interfaces do not support every object and interaction available within Microsoft Dynamics GP (Great Plains). If your integration scenario requires working with objects from other modules or more sophisticated queries, you will need to use our Database Adapter for Microsoft SQL Server to connect to backend database tables directly. While this is an option, it is recommended to avoid accessing Microsoft Dynamics GP (Great Plains) database directly to maintain data integrity and business rule executions.