Skip to main content
Use the @bijection/connectors/dynamics-nav entrypoint to declare Microsoft Dynamics NAV 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 v4 page web service

​
observed: Server-paged pass by Last_Date_Modified (a day of margin), ETag versions, read-only

The following example matches configuration customers.

​
Configuration: customers

Case: dynamics-nav/page/observed/customers. Connection and resource configuration are declared by this exact case. Credential kind: dynamics_nav. 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.

​
Configuration: postedInvoices

Case: dynamics-nav/page/observed/postedInvoices. Connection and resource configuration are declared by this exact case. Credential kind: dynamics_nav. 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. dynamicsNav.page.observed({ service, key?, modified?, columns, lag? }) reads one page published as an OData v4 web service by Dynamics NAV 2017 or 2018 (the Web Services page publishes it under service). Setup baseUrl is the OData v4 root, https://<server>:7048/<instance>/ODataV4/, and company the company name as it appears inside Company('...'), an apostrophe doubled. Network route. A NAV 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. NAV’s ODataServicesSSLEnabled is off by default; plain http:// is admitted only on a relay route, where the cleartext leg is the customer’s own network, and Basic credentials then cross it unencrypted. Prefer enabling SSL on the OData port. The credential (dynamicsNav.credential, kind dynamics_nav) is a basic envelope for a NAV user under NavUserPassword credentials (the user name and its password or web service access key), or a negotiate envelope for Windows authentication, the NAV default: Kerberos with a keytab, NTLM, or both. Azure AD is not supported. NAV has no change tracking, and the standard Customer, Vendor and Item cards’ Last Date Modified is a date set on change. Each pass asks for <modified> ge <date> (default field Last_Date_Modified), the date being the day before the pass’s bound, follows @odata.nextLink (the service’s key bookmark, 1,000 rows by default, Prefer: odata.maxpagesize=100 asked), and starts the next pass lag seconds (default 300) before the first page’s HTTP Date. The day of margin covers the server’s local date against UTC, so every pass re-reads at least a day of changes, deduplicated by version. A blank date (0001-01-01) is read by the first pass only. With modified: null (posted documents, which have no modification date) the page is read whole on every pass under <key> ne ''. Each row is keyed by key (default No); the version is @odata.etag, which Microsoft’s NAV documentation does not describe for OData v4, so a row without one is refused. decimal columns are requested with IEEE754Compatible=true and must arrive as exact text. No deletion is observed and nothing is written. Nothing here has run against Dynamics NAV or been qualified.

​
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.