Skip to main content
Use the @bijection/connectors/epicor entrypoint to declare Epicor Kinetic 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.

Entity set

changes: One entity set by SysRevID, carried across passes

The following example matches configuration standard.

Configuration: standard

Case: epicor/entity/changes/standard. Connection and resource configuration are declared by this exact case. Credential kind: epicor-kinetic. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: rows
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. The connection’s base URL is https://<server>/<instance>/api/v2/odata/<company>/. entity.changes reads one entity set in SysRevID order ($filter=SysRevID ge N&$orderby=SysRevID&$top=100), keyed by SysRowID. SysRevID is the row’s SQL Server rowversion, a JSON integer the host reads as decimal text: it is the record version, each page continues from its largest value (the boundary row is re-read and deduplicated), and a finished pass carries the largest value so the next pass reads only rows written since. A SysRevID above Number.MAX_SAFE_INTEGER is refused rather than read rounded. A rowversion is assigned at write time, not commit time, so a row a long transaction commits below the carried bound is not read until it next changes; no coverage is claimed. Deletions are not observable. That SysRevID is a rowversion and filterable and sortable on every service is reported by Epicor users, not by a public Epicor document (unconfirmed). Kinetic v2 needs an x-api-key beside the user’s credentials on every request. The credential is a basic envelope with the key as a private resource header:
Built from the provider’s published API documentation; nothing here has run against Epicor Kinetic 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.