Introduction
This guide explains how to set up a Dataverse integration using Dashpivot and Flowsite. This flow syncs rows from a Microsoft Dataverse table into a Dashpivot list on a schedule, so the list stays populated from your Dataverse data without anyone copying rows across by hand.
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.
Prerequisites
Before you begin, make sure you have the following:
Plan: Premium or higher
Permission: Dashpivot Contributor
Skills Required: Workflow Automation
Device Type: Computer/Browser
Subscription: Dashpivot, Flowsite, Microsoft Dataverse (Power Platform)
Connections: a Dashpivot connection and a Microsoft (Dataverse) connection already set up in your Flowsite workspace
Destination list: the Dashpivot list you want to populate already exists (the flow fills an existing list — it doesn't create one)
Step-by-step instructions
Access your Flowsite workspace.
In the Connections tab, confirm you have connections to both Dashpivot and Microsoft Dataverse. On the Microsoft Dataverse card, select Connect and log in with a Microsoft account that has access to the Dataverse environment you'll use.
Make sure the Dashpivot list you want to populate already exists, and copy its list ID — the 24-digit string in the list's URL in Dashpivot. You'll paste it in later.
Go to the Flows tab and select Add flow (top-right).
In the "Choose from our range of free flow templates" window, select the Dataverse Tables template ("Sync Microsoft Dataverse tables into Dashpivot Lists").
The flow editor opens with two blocks: a Recurring time trigger and a Dataverse list sync action.
On the Recurring time trigger, set the schedule:
Repeat every — how often the sync runs: Day, 12 hours, 4 hours, or 1 hour. Sub-day options require a higher plan; Standard and Free plans are limited to Day.
Starting at — the hour of day the sync runs, shown in UTC. Start is fixed to "Immediately."
Open the Dataverse list sync action. Under General, select the Dataverse environment.
Under Population, set where the data comes from and where it goes:
Dataverse table — the source table to sync
Dashpivot list ID — paste the 24-digit list ID from step 3
Under Map columns to list properties, build the column mapping. For each row, pick a Dataverse column (source) and the Dashpivot list property it should populate (destination). Select Add mapping to add more rows. At least one mapping is required. Any incompatible pairs are flagged with an orange note and won't sync.
Select the green Save button (top-right). When prompted "Activate flow?", choose Save and Activate to start runs on the schedule, or Save Only to keep it as a draft. You can change the status (Active / Draft / Paused) later on the Settings tab.
(Optional) To run the sync immediately or rebuild the list from scratch, use Resync. Note: this archives all rows in the destination Dashpivot list and resyncs every row from the source Dataverse table, so use it with caution.
Notes
The Dashpivot list must already exist — the flow populates it, it doesn't create it. The Dashpivot connection also needs access to that list.
Schedule times are in UTC.
Sub-day sync intervals (12 hours / 4 hours / 1 hour) require a higher plan.
The sync is one-way (Dataverse → Dashpivot). Rows removed or deactivated in Dataverse are archived in the Dashpivot list, not permanently deleted.
Column types must be compatible. If a Dataverse column can't map to the chosen Dashpivot property type, the pair is flagged and won't sync.
Because the Dataverse connection is tied to the user who authorised it, if that user's Microsoft account is removed or loses access, the connection will break and existing flows will stop running. To resolve this, create a new Microsoft (Dataverse) connection in Flowsite and update the affected flow to use it. See How to Connect Systems in Flowsite for guidance.
FAQs
Does Flowsite support Admin (App-Only) Consent for Dataverse?
No. Flowsite currently uses a User Consent flow to connect to Dataverse, which requires a user login and ties consent to the specific user who authorises the connection.
What happens if the user who authorised the Dataverse connection loses access?
The connection will break and existing flows will stop running. To fix this, create a new Microsoft (Dataverse) connection in Flowsite and update the affected flow to use it.
Do I need to create the Dashpivot list before setting up the flow?
Yes. The flow populates an existing Dashpivot list — it doesn't create one. Make sure the list exists and that your Dashpivot connection has access to it before setting up the flow.
What does Resync do?
Resync archives all rows in the destination Dashpivot list and resyncs every row from the source Dataverse table from scratch. Use it deliberately — for example, to rebuild the list after a mapping change.
Can I sync data more frequently than once a day?
Yes, if you are on a higher plan. Sub-day intervals (12 hours, 4 hours, or 1 hour) are available on eligible plans. Standard and Free plans are limited to once per day.
What happens to rows that are removed or deactivated in Dataverse?
They are archived in the Dashpivot list, not permanently deleted.