Skip to main content
Use the @bijection/connectors/sap-fieldglass entrypoint to declare SAP Fieldglass 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.

​
Business Analytics report rows

​
edited: Fixed windows of the report’s date filter, repeatable and non-consuming, read-only

The following example matches configuration standard.

​
Configuration: standard

Case: sap-fieldglass/report/edited/standard. Connection and resource configuration are declared by this exact case. Credential kind: sap_fieldglass. 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

sapFieldglass.report.edited({ reportId, filter, key, version, columns, start, windowMinutes?, overlapMinutes?, every? }) reads the rows of one Business Analytics report, a report the customer sets up in Fieldglass with a date filter (such as Edited On) added in the report setup. Each request is GET <baseUrl>report/{reportId}/{filter}={from}|{to} (baseUrl the environment’s https://<host>/api/vc/), and the answer is CSV with a header row. Why reports: Fieldglass’s download connectors record a “Last Run Date” each time they run successfully and return what changed since it, so an answer lost after Fieldglass recorded the run cannot be asked for again without SAP resetting the date. A report read by its own filter consumes nothing: the same window answers the same rows. A pass reads windows of windowMinutes (60) from where the last finished pass ended (start on the first pass), each starting where the previous ended, up to an end fixed two minutes before the pass began, and carries that end; the next pass starts overlapMinutes (60) before it. Bounds are written yyyy-MM-dd HH:mm:ss.S, as SAP’s example shows. SAP does not say in which time zone Fieldglass reads them, so the bounds are kept as written rather than as instants: windows stay contiguous in any zone, and only the two-minute settling margin depends on it. Windows touch, so a row stamped on a boundary is read twice and deduplicates by its version. Each row is keyed by the key column, which must be unique per row of the report, and versioned by the version column; a row missing either is refused. columns publishes further report columns by name, empty cells as null. Limits: one window’s answer is one page, at most 128 rows and 512 KiB; a busier window fails its pass, and windowMinutes must then be narrowed (a new declaration starts from start again). A long first backfill takes one request per window. Deleted rows are not observed. The asynchronous mode (isAsynchronous: true) is not used: its poll answers CSV when ready and JSON while pending, under the same status. Bind a sap_fieldglass credential: an oauth_client_credentials envelope for https://<host>/api/oauth2/v2.0/token?grant_type=client_credentials&response_type=token, whose client id is a Fieldglass user name and secret that user’s application password or license key, sent as Basic; add X-ApplicationKey as a private resource header if the environment requires it. Tokens last 7,200 seconds. No Fieldglass 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.