Skip to main content
Use the @bijection/connectors/dynamics-gp entrypoint to declare Microsoft Dynamics GP resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

OData service data source

The following example matches configuration customers.

Configuration: customers

Case: dynamics-gp/dataSource/pull/customers. Connection and resource configuration are declared by this exact case. Credential kind: dynamics_gp. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. dynamicsGp.dataSource.pull({ source, key, fields, every? }) reads one data source published by GP’s OData service (GP 2018 and later, OData v4): a SQL view, table or stored procedure the Data Sources window lists and Publish OData enables. Setup baseUrl is the service root, https://<server>/GPOData/, and company the company database id (TWO); the data source is the next path segment. key names the property that identifies a row and fields the others kept, each as GP’s text (strings as written, numbers and booleans as their JSON text). The service’s $metadata lists a data source’s properties. Credential. The service’s IIS site authenticates Windows accounts only, and the GP user must be linked to that directory account (User Setup, Directory Account). Bind a dynamics_gp credential as a negotiate envelope: kerberos (principal, base64 keytab, KDC and, inside the customer’s network, a kdc_target of the connection’s relay), ntlm (DOMAIN\user and password), or both, Kerberos first and NTLM where no ticket can be had or the service refuses it. Network route. A GP server inside the customer’s network is reached through a network relay: the connection’s typed setup carries network: { relay: "<group>", target: "<name>" }, and the base URL’s host and port equal that relay target’s. Every pass walks the whole data source and follows @odata.nextLink where the server pages; a page without one ends the pass. The service documents no modification filter, no ETag and no row version, so no record version is declared, a row missing from a walk is not read as removed, and nothing is written. GP 2016 R2’s OData v3 service (odata.nextLink) is not declared. Nothing here has run against Dynamics GP or been qualified; Microsoft documents the service’s URL grammar, paging and query options only in community posts.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.