The Problem
When your employee master data lives in Dynamics 365 HR or an ERP backed by Dataverse, keeping Dashpivot's Personnel list in sync is a manual chore. New starters don't appear in dropdown fields until someone re-uploads the list. Leavers stay visible long after they've left. And every time HR updates a record centrally, someone has to remember to reflect that change in Dashpivot too.
What This Flow Does
This flow syncs your employee master data from a Microsoft Dataverse table into a Dashpivot Personnel list on a schedule. Once active:
New starters added in Dataverse appear in Dashpivot at the next scheduled sync — no manual upload needed
Updated records (name changes, role changes) carry through automatically
Leavers are archived in the Dashpivot list, not permanently deleted — so historical forms, timesheets, and records that reference them stay intact
Which Dashpivot Forms Benefit
Any template that references your Personnel list will always show the current workforce in its dropdowns — including:
Timesheets
Sign-on registers
Inductions
Safe Work Method Statements (SWMS)
Permits to work
Workers in the field pick from the same employee list your HR team maintains, with no manual intervention in between.
Storm AI Benefit
Dashpivot list items become known words for Storm's AI Form Fill and audio transcription. A cleaner, up-to-date people list means Storm is more likely to match a spoken name or typed entry to the correct employee record — improving accuracy across site diaries, inductions, and any form that references personnel.
Example Column Mapping
Dataverse Column | Dashpivot List Property |
Full Name | Name (primary column) |
Employee ID | Employee ID |
Job Title | Role |
Department | Department |
Employment Status | Status |
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: Status = Active — so only current employees sync, and crews aren't scrolling past terminated records
Re-sync from scratch: Use this after a bulk restructure or for the initial clean load
Prerequisites
Flowsite Premium or Platinum plan
A Microsoft (Dataverse) connection set up in Flowsite
A Dashpivot Personnel list already created (the flow populates it — it doesn't create it)
Frequently Asked Questions
What happens to employees who leave the company?
When a record is removed or deactivated in Dataverse, the corresponding row is archived in the Dashpivot list — not permanently deleted. This means historical forms, timesheets, and records that reference that employee stay intact.
Do new starters appear in Dashpivot automatically?
Yes. Any new employee added in Dataverse will appear in the Dashpivot Personnel list at the next scheduled sync. No manual upload or CSV re-import is needed.
Can I sync only active employees and exclude terminated records?
Yes. Use the optional row filter on the flow to set a condition such as Status = Active. Only rows matching that condition will sync, so terminated employees won't appear in dropdown fields.
Does this work with Dynamics 365 HR?
Yes. Dynamics 365 HR stores its data in Dataverse tables. As long as your employee records are accessible as a Dataverse table in your Power Apps environment, Flowsite can sync them into Dashpivot.
Will updating an employee's name or role in Dataverse update it in Dashpivot too?
Yes. Each scheduled sync picks up updated rows from Dataverse and reflects those changes in the Dashpivot list automatically.