Skip to main content
Use the @bijection/connectors/sage-300 entrypoint to declare Sage 300 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.

​
AR customers and AP vendors

​
pull: Full $skip walks to the stated count, no versions, read-only

The following example matches configuration customers.

​
Configuration: customers

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

​
Configuration: vendors

Case: sage-300/records/pull/vendors. Connection and resource configuration are declared by this exact case. Credential kind: sage_300. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: vendors
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. Reads the Sage 300 Web API that installs with Sage 300 Web Screens on the customer’s IIS. Setup baseUrl is the API root, https://<server>/Sage300WebApi/v1.0/-/, and company the company database id (SAMLTD). The credential (sage300.credential, kind sage_300) is a basic envelope for a Sage 300 user granted the “Sage 300 Web API” security authorization. Network route. A Sage 300 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. Plain http:// is admitted only on a relay route, where the cleartext leg is the customer’s own network; Basic credentials then cross that network unencrypted, so prefer the HTTPS binding Sage requires for Web Screens. A publicly reachable server needs https://. records.pull reads customers (AR/ARCustomers, keyed by CustomerNumber) or vendors (AP/APVendors, keyed by VendorNumber, the name the endpoint reference implies but no captured $metadata confirms). fields names further top-level properties, kept as Sage’s text; DateLastMaintained is always read. Every request sends Content-Type: application/json, which Sage requires even on GET. Every pass walks the whole entity by $skip with $count=true and stops at the stated count or an empty page. DateLastMaintained is date-granular and its filter literal differs between releases, and $orderby and next links are not documented, so no modification filter is used. The server’s PageSize (100 by default) caps a page, so the walk advances by the rows each page returned. A row inserted below the offset mid-walk shifts later rows and can be missed until the next pass; a walk claims no coverage. No ETag or row version is documented, so no record version is declared, and Sage publishes no deletions. Numbers are published as their JSON text; Sage’s samples send Edm.Decimal amounts as JSON numbers, so an amount beyond 15 significant digits is not exact. AR invoices are not declared: AR/ARInvoiceBatches nests every invoice and its details inside one batch row, which a page of batches can exceed the response bound with. Nothing here has run against Sage 300 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.