The Problem
When your client accounts or project records live in Dynamics 365 Sales or another CRM backed by Dataverse, keeping Dashpivot's client list current is a manual process. Free-typed client names on forms create data quality issues downstream — mismatched names, incorrect job numbers, and inconsistent reporting. And when the sales or project team updates a record centrally, the field doesn't see it until someone remembers to re-upload the list.
What This Flow Does
This flow syncs your accounts or projects table from a Microsoft Dataverse table into a Dashpivot Client list on a schedule. Once active:
New clients or projects added in Dataverse appear in Dashpivot at the next scheduled sync — no manual upload needed
Updated records (client name, job number, project status) carry through automatically
Clients or projects removed or deactivated in Dataverse are archived in the Dashpivot list, not permanently deleted — so historical delivery dockets, service reports, and variations that reference them stay intact
Which Dashpivot Forms Benefit
Any template that references your Client list will always show the correct, current client names and job numbers — including:
Delivery dockets
Service reports
Variation forms
Site diaries referencing client or project
Invoice-supporting documentation
Workers and supervisors pick from the same client list your sales or project management team maintains, with no manual intervention in between.
Storm Benefit
Dashpivot list items become known words for Storm's AI Form Fill and audio transcription. A clean, up-to-date client list means Storm is more likely to match a spoken client name or project reference to the correct record — improving accuracy across delivery dockets, service reports, and any form that references a client or project. It also keeps downstream reporting clean when form data flows back out to Power BI.
Example Column Mapping
Dataverse Column | Dashpivot List Property |
Account Name / Project Name | Name (primary column) |
Account ID / Job Number | Job Number |
Project Status | Status |
Primary Contact | Contact |
Region / Site | Location |
Account Manager | Account Manager |
Map only the columns your forms need — you don't have to bring across every field from Dataverse.
Recommended Flow Settings
Schedule: Daily or more frequent (sub-day intervals available on Premium/Platinum)
Row filter: Project Status = Active — so only active clients and projects appear in dropdown fields, and teams aren't selecting closed or won/lost accounts on forms
Re-sync from scratch: Use this after a bulk CRM migration or restructure, or for the initial clean load
Prerequisites
Flowsite Premium or Platinum plan
A Microsoft (Dataverse) connection set up in Flowsite
A Dashpivot Client list already created (the flow populates it — it doesn't create it)
Frequently Asked Questions
What happens to clients or projects that are closed or inactive?
When a client or project record is removed or deactivated in Dataverse, the corresponding row is archived in the Dashpivot list — not permanently deleted. Historical delivery dockets, service reports, and variations that reference that client stay intact.
Can I filter so only active clients and projects appear in Dashpivot forms?
Yes. Use the optional row filter on the flow to set a condition such as Project Status = Active. Only records matching that condition will sync, so closed or inactive accounts won't appear in dropdown fields.
Will updating a client name or job number in Dataverse update it in Dashpivot too?
Yes. Each scheduled sync picks up updated rows from Dataverse and reflects those changes in the Dashpivot Client list automatically.
Do new clients or projects appear in Dashpivot automatically after being added to Dataverse?
Yes. Any new client or project added in Dataverse will appear in the Dashpivot Client list at the next scheduled sync. No manual upload or CSV re-import is needed.
Does this work with Dynamics 365 Sales?
Yes. Dynamics 365 Sales stores account and opportunity data in Dataverse tables. As long as your client or project records are accessible as a Dataverse table in your Power Apps environment, Flowsite can sync them into Dashpivot.
How does this help with Power BI reporting?
When client names and job numbers are selected from a consistent, synced list rather than free-typed, form data stays clean and consistent. This means when data flows out of Dashpivot into Power BI, client-level reporting is accurate and reliable — no mismatched names or duplicate entries to clean up.
Next Steps
Ready to set this up? See How to Set Up a New Flow for Dataverse on Flowsite.