Skip to main content
Use the @bijection/connectors/sage-50 entrypoint to declare Sage 50 Accounts (UK and Ireland) 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.

Bridge datasets (ledgers, invoices, audit trail)

incremental: Bridge pages: snapshots each pass, audit trail by TRAN_NUMBER with tombstones, read-only

The following example matches configuration customers.

Configuration: customers

Case: sage-50/records/incremental/customers. Connection and resource configuration are declared by this exact case. Credential kind: sage_50. 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: transactions

Case: sage-50/records/incremental/transactions. Connection and resource configuration are declared by this exact case. Credential kind: sage_50. 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. Sage 50 has no network API; Sage Data Objects (SDO) is COM on the Windows machine that holds the company data. Run bijection-sage50 serve --config bridge.json on that machine (the windows/386 build for a 32-bit SDO) and reach it through a network relay route (http:// is admitted only there) or an authenticated HTTPS ingress. The bridge holds the Sage 50 user and password and keeps no state. Bind the resource’s endpoint to the bridge URL and install the bridge’s bearer as a sage_50 credential (sage50.credential). Each dataset is one SDO record object declared in the bridge configuration, with its key, its fields and their exact types:
  • snapshot datasets (SalesRecord, PurchaseRecord, NominalRecord, InvoiceRecord): each pass is a new baseline, and a record that baseline does not return, or that the dataset’s deleted field flags, leaves.
  • ascending datasets (AuditHeader by TRAN_NUMBER): a sync pass serves the transactions numbered above the last pass, deleted ones as tombstones. An in-place correction of an older transaction is seen by the baseline the bridge forces after rebaseline_hours (default 24).
Fields arrive as exact text or null: decimals at the declared scale (a double that is not exactly a decimal of that scale is refused, never rounded), dates YYYY-MM-DD, datetimes as Sage’s zoneless wall time. The version is a digest of the served fields. Busy or locked company data answers 503 with Retry-After. The snapshot holds at most maxRecords (default 50000, at most 131072). The source is read-only. No Sage company has been reached by these checks.

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.