Dataverse Integration on Flowsite — Frequently Asked Questions

What is Microsoft Dataverse?
Dataverse is part of the Microsoft Power Platform. Its tables are listed under Tables in Power Apps for your chosen environment. Apps like Dynamics 365 HR, Dynamics 365 Field Service, and Dynamics 365 Sales all store their data in Dataverse tables.

What does the Dataverse integration in Flowsite do?
It automatically syncs rows from a Microsoft Dataverse table into a Dashpivot list on a schedule. Once set up, the list stays populated from your Dataverse data without anyone copying rows across manually.

What plan do I need to use the Dataverse integration?
The Dataverse integration is available on Flowsite Premium and Platinum plans.

Is the sync one-way?
Yes. Data flows from Dataverse into Dashpivot only. Two-way sync is not currently supported.

Which Dataverse environments and apps are supported?
Any Dataverse environment accessible via your Microsoft account is supported — including those used by Dynamics 365 HR, Dynamics 365 Field Service, Dynamics 365 Sales, and custom Power Apps.

How does Flowsite connect to Dataverse?
Flowsite uses a User Consent flow (OAuth) to connect to Dataverse. This requires a user login and ties consent to the specific Microsoft account that authorises the connection

.

Does Flowsite support Admin (App-Only) Consent for Dataverse?
No. Flowsite currently uses User Consent only, which requires a user login.

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 using an active account and update the affected flow to use it.

Can I use a dedicated service account for the Dataverse connection?
Yes. You can create a dedicated Microsoft Entra ID user account with the minimal required permissions to authorise the connection. This is recommended to avoid flows breaking if an individual user's account is removed.

How often does the sync run?
You set the schedule when configuring the flow. Options are Daily, 12 hours, 4 hours, or 1 hour. Sub-day intervals require a Premium or Platinum plan. Standard and Free plans are limited to once per day.

What happens on the first sync?
The first run is a full pull — every row from the Dataverse table that matches your filter conditions is synced into the Dashpivot list.

What happens on subsequent syncs?
After the first full pull, each scheduled run is incremental — only new, updated, or removed rows are transferred. This keeps runs fast and avoids unnecessary overwrites.

What happens to rows that are removed or deactivated in Dataverse?
They are archived in the Dashpivot list, not permanently deleted. This means historical forms and records that reference those rows stay intact.

Can I trigger a sync immediately without waiting for the next scheduled run?
Yes. Use Run now in the flow settings to trigger an incremental sync on demand.

What does Re-sync from scratch do?
Re-sync from scratch archives all rows in the destination Dashpivot list and rebuilds it from the Dataverse table from scratch. Use it deliberately — for example, after a bulk mapping change or for the initial clean load.

Can I filter which rows sync from Dataverse?
Yes. You can set an optional row filter on the flow so only rows matching specific conditions are synced — for example, Status = Active or Approval Status = Approved.

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 your Dashpivot connection has access to it before setting up the flow.

What column types are supported for mapping?
Flowsite supports mapping Text, Number, Date, Choice, Lookup, Boolean, Multi-select, and more. Incompatible column pairs are flagged with an orange note in the flow editor and won't sync.

Can I map multiple Dataverse columns to multiple Dashpivot list properties?
Yes. You can add as many column mappings as you need. At least one mapping is required to save the flow.

Can I sync more than one Dataverse table into the same Dashpivot list?
No. Each flow syncs one Dataverse table into one Dashpivot list. To sync multiple tables, set up separate flows.

How do I view the results of each sync run?
Each run is logged in the Runs tab in your Flowsite workspace. From there you can see the status of each run (Success, Failed, or Pending) and any errors, with categorised messages describing what went wrong and what action to take.

A row failed to sync — what should I check?
Check the Runs tab for the error message on that row. Common causes are incompatible column types, missing required fields in the destination list, or a connection issue. Fix the underlying issue and use Run now to retry.

My flow stopped running — what happened?
Check the Connections tab in Flowsite. If the Microsoft (Dataverse) connection shows as disconnected, the authorising user's account may have lost access. Create a new connection using an active account and update the flow to use it.