Microsoft Dataverse to Looker Integration
AI-first ETL from Microsoft Dataverse into Looker. Governed entities, incremental sync, typed landing tables.
How Datrise loads Microsoft Dataverse into Looker
Datrise syncs Microsoft Dataverse's tables, rows, columns, relationships, choice sets, and change tracking into Looker as governed warehouse tables with LookML-ready naming. Flexible or custom fields land in flattened columns (nested fields expanded for modeling), and timestamps such as created, updated, and status changes are typed as date/time dimension columns.
Sync is incremental: Datrise uses incremental refresh of the underlying warehouse tables Looker explores, so re-runs update only what changed. Date-partitioned fact tables for PDT performance. Looker models live in LookML on top of SQL, so Datrise lands clean, stable column names rather than churn that would break your views.
Ideal for governed, version-controlled BI on a warehouse.
Endpoints
Microsoft Dataverse: Business data platform behind Dynamics and Power Apps.
Looker: Google Cloud BI with LookML semantic models and governed dashboards.
How Microsoft Dataverse entities map to Looker
| Microsoft Dataverse entity | Looker object | Notes |
|---|---|---|
| tables | microsoft_dataverse_tables | id PK · custom fields → flattened columns (nested fields expanded for modeling) |
| rows | microsoft_dataverse_rows | id PK · linked to microsoft_dataverse_tables |
| columns | microsoft_dataverse_columns | id PK · linked to microsoft_dataverse_tables |
| relationships | microsoft_dataverse_relationships | id PK · linked to microsoft_dataverse_tables |
FAQ
How does Datrise handle Microsoft Dataverse's custom fields in Looker?
Flexible values are stored as flattened columns (nested fields expanded for modeling), so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Looker types.
How does the Microsoft Dataverse to Looker sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the underlying warehouse tables Looker explores.
Related pipelines
More destinations for Microsoft Dataverse
- Microsoft Dataverse → Looker Studio
- Microsoft Dataverse → Microsoft Power BI
- Microsoft Dataverse → Tableau
- Microsoft Dataverse → Apache Superset
- Microsoft Dataverse → Metabase
- Microsoft Dataverse → Amazon QuickSight
- Microsoft Dataverse → Domo
- Microsoft Dataverse → Sisense
- Microsoft Dataverse → ThoughtSpot
- Microsoft Dataverse → Qlik
- Microsoft Dataverse → Mode
- Microsoft Dataverse → Redash
Early access
Connect Microsoft Dataverse to Looker the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.