Nexra
Start in the sandbox
All connectors
Microsoft Dynamics GP logo

Microsoft Dynamics GP

ERP & business operations

Keep Microsoft Dynamics GP in step with your orders, stock and finance, with the right person approving every posting.

9 ways to read.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Microsoft Dynamics GP with Nexra

Connected, approved, proven.

The things teams do most with Microsoft Dynamics GP, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • List bank transactionsbank_transactions.listRead

Example flow

  1. Microsoft Dynamics GP · List bank transactionsbank_transactions.listDone
  2. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Microsoft Dynamics GP.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Microsoft Dynamics GP
  • Microsoft Dynamics GP's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Reads Dynamics GP receivables, payables, general ledger, bank, sales order, customer and item data through the Nexra relay.

Microsoft API docs
Source actions
9
Data types
9

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

bank transactions1
  • List bank transactionsSourceIncremental

    Checkbook register transactions (CM20200).

credit notes1
  • List credit notesSourceIncremental

    Receivables credit memos and returns (document types 7 and 8).

customers1
  • List customersSourceIncremental

    Customer master (RM00101).

invoices1
  • List invoicesSourceIncremental

    Receivables sales invoices, open and history (RM20101, RM30101; document type 1).

items1
  • List itemsSourceIncremental

    Item master (IV00101).

journal entries1
  • List journal entry linesSourceIncremental

    General ledger transaction lines, open and history years (GL20000, GL30000).

payments1
  • List customer paymentsSourceIncremental

    Receivables payments, open and history (document type 9).

sales orders1
  • List sales ordersSourceIncremental

    Sales Order Processing orders, open and history (SOP10100, SOP30200; type 2).

vendor payments1
  • List vendor paymentsSourceIncremental

    Payables payments, open and history (PM20000, PM30200; document type 6).

Access and limits

Authentication
Read-only SQL login held on your relay server; nothing is stored in Nexra
Plans and access
Microsoft Dynamics GP 2013 or later on SQL Server. Needs a read-only SQL Server login for the GP company database, held on the relay server.
Test environment
Use the GP sample company (TWO) or a test company for Test mode.
Rate limits
Bounded by your SQL Server; reads are keyset-paged by change time.
Pagination
Opaque cursors from the relay agent (change time and document key).
Provider events
Dynamics GP has no outbound events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Needs a paired Nexra on-premise relay agent that is online; requests fail fast with a clear message while it is offline.
  • The relay agent only reaches the systems, paths and methods its administrator allows in its local configuration file.
  • Read only: the relay runs fixed, parameterised SELECT queries; Nexra cannot send SQL, and writes (eConnect) are not implemented.
  • The relay agent's SQL Server driver must be enabled for Dynamics GP; until then reads report that the connection cannot be made.
  • Needs on-site validation with a real GP company database: table and column names follow the GP table reference, and change tracking uses DEX_ROW_TS (GP 2013 and later).

Developer reference

  1. Create the Microsoft credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Microsoft Dynamics GP, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Microsoft docsAPI referenceMicrosoft docsAuthentication

Machine-readable detail: GET /api/public/connect/connectors/dynamics-gp and the Connections API.