Skip to main content
Feedback

Great Plains connector

The Great Plains connector enables you to move data into and out of the Microsoft Great Plains (now called Microsoft Dynamics GP) business management application.

Use the connector to Query and Upsert various types of records, including Accounts, Customers, Sales Orders, Invoices, and more.

The connector uses an integration layer called eConnect to exchange data with the Great Plains database. eConnect is a Microsoft API that facilitates data exchange by performing business validation and ensures data integrity. You implement it as a set of database-stored procedures installed on the Great Plains database server. Ensure you install eConnect before you attempt to connect to Great Plains.

Connector configuration

Configuring a connector to communicate with Great Plains requires setup of two components:

  • Great Plains connection — The connection represents a specific Great Plains company database. You create one connection for each company database.

  • Great Plains operation — The operation represents an action against a specific record type. You create one or more operations, one for each type of interaction required by your integration scenario.

Supported editions

Boomi supports the following Great Plains editions and modules:

  • Great Plains 9.x

  • Great Plains 10.x

    note

    Use the Great Plains connector with Microsoft Great Plains 9.x and 10.x only. If you are using Microsoft Dynamics GP 2010, or 2013/2015/2016/2018+, use the Microsoft Dynamics GP connector. To learn more, see the topic Microsoft Dynamics GP connector.

  • Modules:

    • Bank Reconciliation (BR)

    • Company (CMP)

    • Field Service (FS)

    • Fixed Assets (FA)

    • General Ledger (GL)

    • Inventory (IV)

    • Lockbox (LB)

    • Project Accounting (PA)

    • Purchase Order Processing (POP)

    • Purchasing (PM)

    • Receivables (RM)

    • Sales Order Processing (SOP)

    • Shared Master (SM)

    • US Payroll (UPR)

Prerequisites

To implement a connection to Great Plains from Integration:

  1. Install Great Plains and the database.

  2. Set up a local basic runtime within your network to connect to the Great Plains SQL Server and eConnect. You must install the basic runtime on Windows. This connector does not run on Linux. Install the basic runtime on the same server as eConnect and the Great Plains SQL Server.

  3. Configure the connector with a Windows domain user that has access to the Great Plains SQL Server database machine. A SQL Server login must be created for this domain user and the database user must be granted the DYNGRP role within the DYNAMICS database.

  4. Install the eConnect libraries.

    1. The option to install eConnect is under the Additional Products section of the Great Plains installer.

    2. See the eConnect Documentation (see the linked topic).

    3. You do not need to install the full eConnect Runtime module.

    4. Install IKVM.NET to connect to the .NET libraries.

The eConnect interfaces do not support every object and interaction available within Great Plains. If your integration scenario requires working with objects from other modules or more sophisticated queries, you must use the Database connector to connect to back-end database tables directly. Consult your eConnect documentation for more information about the table schemas. Use caution when accessing application database tables directly to maintain data integrity.

If you are encounter connectivity issues, check the container logs for information about these error messages.

Tracked properties

This connector has no predefined tracked properties. See the topic Adding tracked fields to a connector operation to learn how to add a custom tracked field.

On this Page