Hi @kapa.ai, can I do CDC with the Dataverse connector docs.airbyte.com/integrations/sources/microsoft-dataverse?

The Microsoft Dataverse connector does not use traditional CDC (Change Data Capture) in the same way as database connectors like Postgres or MySQL. However, it does support incremental sync with deleted record tracking, which provides similar functionality. Here's how it works: • Incremental Sync is available for tables that have change tracking enabled in Dataverse. The connector uses the

Prefer: odata.track-changes

header and OData delta tokens to fetch only modified and deleted records since the last sync. [Microsoft Dataverse docs] • Deleted records are captured and emitted with

_ab_cdc_deleted_at

populated, and only the primary key field is included. [Microsoft Dataverse docs] • Updated records are emitted with

_ab_cdc_updated_at

populated. [Microsoft Dataverse docs] Key requirement > Change tracking must be enabled on a table in Dataverse for incremental sync to be available. Tables without it only support Full Refresh. [Limitations] What's not supported The Dataverse connector is not listed among Airbyte's native CDC-supported connectors (Postgres, MySQL, MSSQL, MongoDB, etc.), so it does not use log-based CDC. [CDC support] In summary: you can achieve CDC-like behavior (incremental updates + deletes) with the Dataverse connector, as long as change tracking is enabled on your tables. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.