Skip to main content
Feedback

Microsoft Dynamics GP operation

The Microsoft Dynamics GP operation defines how to interact with Great Plains data.

The operation represents an action (Create, Query, Execute, Upsert) performed against a Great Plains record type or object (such as Customers, Sales Transactions, Purchase Orders). Not all actions are available for every object. Create a separate operation component for each action and object combination required for your integration.

Query

The inbound Query action allows to look up object records based on specific search criteria. You supply static or dynamic request parameters (filters) to control selecting the object records. A single Query request can return zero or more object record documents. After selecting the Query connector action and using the Import Wizard, you can add query filters.

Create

Use the outbound Create action to insert data into your Microsoft Dynamics GP account.

Execute

For Microsoft Dynamics GP 2010 and 2013, the outbound Execute action exposes the following eConnect web service functions:

  • Create Entity
  • Create Transaction Entity
  • Delete Entity
  • Delete Transaction Entity
  • Dispose
  • Get Entity
  • Get Next GL Entry Journal Number
  • Get Next IV Number
  • Get Next PO Number
  • Get Next PO Receipt Number
  • Get Next RM Number
  • Get Next SOP Number
  • Get PM Next Voucher Number
  • Roll Back Documents
  • Update Entity
  • Update Transaction Entity

Upsert

The outbound Upsert action creates a new record if one does not exist; otherwise it updates the existing record.

Options tab

Click Import Operation, then use the Import wizard to select the object with which you want to integrate. The following table describes the default field definitions for each action type:

Object - Displays the object type that you selected in the Import Operation wizard.

Tracking Direction - Select the document tracking direction for the operation, either Input Documents or Output Documents. This setting enables you to choose which document appears in Process Reporting. Start steps always track output documents regardless of your selection.

note

If the tracking direction is read-only, the feature to change the direction is either unavailable or the developer set the configuration to read-only. The default value you see shows you which document appears in Process Reporting.

Request/Response Profile - The XML profile definition that represents the structure sent or received by the connector.

Return Application Error Responses - This setting controls whether an application error prevents an operation from completing:

  • If you clear the setting, the process stops and reports the error on the Process Reporting page.
  • If you select the setting, processing continues and passes the error response to the next component processed as the connection output.

Archiving tab

See the topic Connector operation’s Archiving tab for more information.

Tracking tab

See the topic Connector operation’s Tracking tab for more information.

Caching tab

See the topic Connector operation’s Caching tab for more information.

On this Page