Skip to main content
Use the @bijection/connectors/business-central entrypoint to declare Microsoft Dynamics 365 Business Central 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.

API v2.0 company entity

observed: Server-paged pass by lastModifiedDateTime with ETag-conditioned updates

The following example matches configuration standard.

Configuration: standard

Case: business-central/entity/observed/standard. Connection and resource configuration are declared by this exact case. Credential kind: business_central. 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: updates

Case: business-central/entity/observed/updates. Connection and resource configuration are declared by this exact case. Credential kind: business_central. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

businessCentral.entity.observed({ entitySet, columns, update?, lag? }) reads one API v2.0 entity set of one company: the binding’s baseUrl is the API root, such as https://api.businesscentral.dynamics.com/v2.0/<tenant>/<environment>/api/v2.0/ (an on-premises API root works the same way), and company its company id. Business Central removed delta links in version 24 (2024 release wave 1) and its $filter cannot or two different fields, so neither change tracking nor a (time, key) keyset exists. Each pass asks for the rows with lastModifiedDateTime ge … and follows @odata.nextLink, the service’s key bookmark, with Prefer: odata.maxpagesize=100. The first page’s Date is the pass’s basis and the next pass begins lag seconds (default 300) before it. The company id is the account identity. Each row’s @odata.etag is its version; update: { fields, governingRule } declares a single-attempt PATCH with the If-Match Business Central requires: 200 confirms, a stale tag is 412, a lost answer stays unknown. decimal columns are requested with Accept: application/json;IEEE754Compatible=true and checked as exact decimal text; Microsoft does not document that Business Central honours the parameter, and a page whose decimal arrives as a JSON number is refused rather than published as a double. Declare number to accept doubles. Not observed: deletions, which Business Central reports only through webhook subscriptions (not consumed). Dynamics NAV publishes pages, not API v2.0 entities; the dynamics-nav recipe reads them. GP’s OData service data sources are read by the dynamics-gp recipe. Bind a business_central credential: oauth_client_credentials against https://login.microsoftonline.com/<tenant>/oauth2/v2.0/token with scope https://api.businesscentral.dynamics.com/.default. No environment has been reached.

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.