Skip to main content
The Microsoft Dataverse integration retrieves and updates customer party data in Dataverse for Microsoft Dynamics 365 CRM. The party connector is outbound: it reads and updates contact records. The party inbound connector receives create, update, and delete webhooks from Dataverse and publishes party update events to the Sync Hub ASB producer. For setup steps, see Get started. Supported version: Microsoft Dataverse Contact Entity API.

Configuration properties

gc-dataverse-party-connector

Set these properties in party-v0.values.yaml. This connector sends outbound requests to Dataverse.

gc-dataverse-party-inbound-connector

Set these properties in party-inbound-v0.values.yaml. This connector receives Dataverse webhooks and publishes events to the Sync Hub ASB producer.

Supported operations

The Dataverse connector exposes the party operations of the Grand Central Unified API. For the operation-to-endpoint table, see Overview. For the full contract, see the unified API specifications.

Events

The party inbound connector publishes the following event to the Sync Hub ASB producer. The party inbound connector consumes notifications from the following source. The party connector is synchronous and doesn’t publish or consume events.

Error mapping

The connector maps Dataverse error codes to Grand Central status codes using the shared transform-dataverse-error-details.json template. For the full list, see Error codes.

Dependencies

  • Microsoft Dataverse Contact Entity API (outbound), reachable at dataverse.serviceUri.
  • Dataverse contact webhooks (inbound), delivered to the registered callback URL.
  • Sync Hub ASB producer, which receives the published party update events.
  • dataverse-connector-sdk (shared HTTP configuration and Dataverse error code mapping).