@bijection/connectors/dataverse entrypoint to declare Microsoft Dataverse (Dataverse 365) 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.
Table
changes: Change tracking with conditional writes
The following example matches configurationstandard.
Inferred record types
Inferred record types
Configuration: standard
Case:dataverse/table/changes/standard.
Connection and resource configuration are declared by this exact case.
Credential kind: odata. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Configuration: writes
Case:dataverse/table/changes/writes.
Connection and resource configuration are declared by this exact case.
Credential kind: odata. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Provider guidance
Capture selected tables withbijection source metadata capture dataverse, then
select generated crm.account.fields in crm.account.resource. This resource
uses the native OData v4 acquisition and durable-command owners. The low-level
dataverse.table.changes constructor also requires normalized metadata.
Bind serviceUrl to the exact HTTPS /api/data/v9.2/ root. The resource supplies
the captured entity-set name and v4 default. Its dataverse.credential reference
uses existing OData credential custody. The private credential envelope is:
WhoAmI to retain organization and application-user identity, and validates
selected standard-table metadata. Change tracking and optimistic concurrency
must already be enabled. Enabling change tracking remains an administrator’s
explicit action. Secured columns, elastic/virtual tables, unsupported types and
ambiguous lookup targets refuse.
Initial reads follow native next links to a delta link. Tracked requests contain
no $filter, $orderby, $expand or $top. Lookup rows retain their target table
and GUID; money remains exact text with its currency dependency; date behavior
participates in compatibility. The resource exposes observations with ETags,
not a consistent population snapshot or an audit history.
Currency-dependent precision is not a fixed column scale. Base-currency money
columns remain unsupported until organization currency is captured explicitly.
Declare named scalar updates with dataverse.update({ fields, governingRule })
and deletes with dataverse.remove({ governingRule }) on the generated resource’s
commands. Every command uses the retained target ETag and single-attempt
delivery. A lost answer remains unknown. Current matching values are not a
receipt, and local publication remains independent of command confirmation.
Creates, upserts, custom actions, delegated authentication and attachments are
outside this profile. Certificate assertions are not TLS client certificates.
Microsoft Project (Project for the web and Planner premium plans; Project
Online retired on 2026-09-30) keeps plans in Dataverse tables such as
msdyn_project, msdyn_projecttask, msdyn_projectbucket,
msdyn_resourceassignment and msdyn_projecttaskdependency. Capture and read
them like any table, provided change tracking is enabled on each. The Project
scheduling service owns these tables: Microsoft documents changes only through
the Project schedule APIs, which application users cannot call, so a resource
over a scheduling table refuses update and remove commands.
The catalog’s schema is synthetic. Source fixtures and generated declarations do
not establish a passing native run or live provider qualification. No Dataverse
environment has been reached by these fixtures.
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.