Introduction
Dataverse is part of the Microsoft Power Platform. Its tables are the ones listed under Tables in Power Apps for the chosen environment. The Dataverse integration in Flowsite lets you automatically pull rows from a Microsoft Dataverse table into a Dashpivot list — so the list stays populated from your Dataverse data without anyone copying rows across by hand.
The Problem
Teams using Microsoft Dynamics 365 or Power Platform often have critical reference data — employee lists, equipment registers, contractor records, client accounts — living in Microsoft Dataverse. Getting that data into Dashpivot meant manual exports and re-imports. Lists drifted out of date the moment the source changed, and keeping them current was a recurring admin chore.
Why It Matters
Easier onboarding — if your reference data already lives in Dataverse, you don't need to rebuild it in Dashpivot from scratch
Reduced admin — no more re-uploading CSVs or manually updating list items when the source changes
Cleaner data for Storm — Dashpivot list items become "known words" for Storm's AI Form Fill and audio transcription, improving accuracy across any form that references a list
One source of truth — update a record once in Dataverse and every Dashpivot form referencing it stays current
How Flowsite connects to Dataverse
Flowsite uses a User Consent flow to connect to Dataverse. This approach:
Requires a user login, and
Ties consent to the specific user who authorises the connection
You may choose to create a dedicated Microsoft Entra ID user account with the minimal required permissions to authorise the connection and use the integration.
This may include granting that user access only to the specific Dataverse environment used with the Flowsite integration.
Please note that Flowsite does not currently support the Admin (App-Only) Consent flow to connect to Dataverse.
Requirements
You need a Dashpivot connection and a Microsoft (Dataverse) connection in your Flowsite workspace. Learn how to add connections.
This integration is available to customers on the Premium plan or higher.
Supported configurations
The following are supported:
Syncing rows from one Dataverse table into one Dashpivot list
Column mapping — choosing which Dataverse columns fill which Dashpivot list properties
Syncing on a schedule — each run keeps the Dashpivot list in step with the Dataverse table, adding new rows, updating changed ones, and archiving rows that have been removed in Dataverse
Optional row filtering — you can set a filter on the flow so only rows matching specific conditions are synced from the source table, rather than the entire table
Incremental syncs — after the first full pull, each scheduled run transfers only rows that have changed (new, updated, or removed), keeping runs fast and avoiding unnecessary overwrites
On-demand run options — use Run now to trigger an incremental sync immediately without waiting for the next scheduled run, or Re-sync from scratch to archive all rows in the Dashpivot list and rebuild from the Dataverse table
The sync is one-way (Dataverse → Dashpivot). Rows removed or deactivated in Dataverse are archived in the Dashpivot list, not permanently deleted.
Setting up a Dataverse flow
For step-by-step instructions, see How to Set Up a New Flow for Dataverse on Flowsite.
Also see: How to Connect Systems in Flowsite
Common Use Case
Not sure where to start? See how teams are using the Dataverse integration in practice:
Dataverse + Dashpivot: People & Employee Lists
Dataverse + Dashpivot: Plant & Equipment Lists
Dataverse + Dashpivot: Contractor & Subcontractor Registers
Dataverse + Dashpivot: Customer & Project Client Lists
What's Next
This integration is the first step in a broader effort to keep Sitemate products in sync with core systems of record. Coming up:
SharePoint Lists → Dashpivot Lists
Dataverse → Gearbelt Asset Register and Location List
SharePoint Lists → Gearbelt Asset Register and Location List
Have questions? See the Dataverse Integration FAQs.