Skip to main content
Use the @bijection/connectors/sharepoint-server entrypoint to declare SharePoint Server 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.

​
List and library items

​
observed: First pass walks every item; later passes read GetChanges windows, deletions first, read-only

The following example matches configuration invoices.

​
Configuration: invoices

Case: sharepoint-server/listItems/observed/invoices. Connection and resource configuration are declared by this exact case. Credential kind: sharepoint_server. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: items
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. sharepointServer.listItems.observed({ list, fields, every? }) reads the items of one list or document library of a SharePoint Server farm (2016, 2019 or Subscription Edition) through the site’s REST API. Setup baseUrl is the site, https://<server>/sites/<site>/; list is the list’s GUID and fields internal field names beside ID and Modified, each kept as SharePoint’s text. SharePoint Online is read through Microsoft Graph (microsoft-graph), which does not reach a farm. Credential. Bind a sharepoint_server credential. Claims web applications authenticate Windows accounts: a negotiate envelope with kerberos (principal, base64 keytab, KDC and, inside the customer’s network, a kdc_target of the connection’s relay), ntlm (DOMAIN\user and password), or both, Kerberos first and NTLM where no ticket can be had or the farm refuses it. A zone with Basic enabled takes a basic envelope over TLS. Network route. A farm inside the customer’s network is reached through a network relay: the connection’s typed setup carries network: &#123; relay: "&lt;group&gt;", target: "&lt;name&gt;" &#125;, and the base URL’s host and port equal that relay target’s. Passes. A first pass reads the list’s CurrentChangeToken, then walks every item by ID, 100 a page, each page asking for the IDs after the previous page’s last ($filter=ID gt n, $orderby=ID, on the indexed ID); the token is where the next pass begins. A later pass reads the token again as its end and reads the change log between the two with GetChanges: first the item deletions, published as deleted records from the change log itself, then additions, updates, restores and system updates, whose items are read again by ID and published with their values. Deletions come first, so an item deleted and restored within one window ends present, and one restored and deleted again ends deleted. Each GetChanges asks for 100 changes and continues from the last change’s token. Every POST carries a form digest from /_api/contextinfo. The version is the item’s odata.etag. Limits. A change log older than the web application’s retention (60 days by default) refuses the pass with a message to reset the source; the new first pass does not withdraw items deleted meanwhile. An item deleted twice within 100 changes names one key twice in a deletions page, which the host refuses. File content, item attachments and permissions are not read, and nothing is written. Nothing here has run against SharePoint Server or been qualified. The JSON light shapes (value, odata.etag) and the verbose SP.ChangeQuery body follow Microsoft’s REST documentation; the expired-token refusal’s wording is inferred.

​
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.