The Problem
When your asset register lives in Dynamics 365 Field Service or another ERP backed by Dataverse, keeping Dashpivot's Plant & Equipment list current is a manual process. Disposed or off-hired equipment stays visible in dropdown fields until someone re-uploads the list. New assets don't appear until the next manual import. And when the office updates the register centrally, the field doesn't see it until someone remembers to sync it across.
What This Flow Does
This flow syncs your central asset register from a Microsoft Dataverse table into a Dashpivot Plant & Equipment list on a schedule. Once active:
New assets added in Dataverse appear in Dashpivot at the next scheduled sync — no manual upload needed
Updated records (asset status, description, assigned location) carry through automatically
Assets removed or deactivated in Dataverse are archived in the Dashpivot list, not permanently deleted — so historical inspection records and pre-starts that reference them stay intact
Which Dashpivot Forms Benefit
Any template that references your Plant & Equipment list will always reflect the live register — including:
Pre-start checklists
Plant inspections
Maintenance records
Defect reports
Site diaries referencing equipment on site
Workers in the field pick from the same asset register your office 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 equipment list means Storm is more likely to match a spoken asset name or plant ID to the correct record — improving accuracy across pre-starts, inspections, and any form that references plant and equipment.
Example Column Mapping
Dataverse Column | Dashpivot List Property |
Asset Name | Name (primary column) |
Asset ID / Plant Number | Plant Number |
Asset Type | Category |
Status | Status |
Assigned Location | Location |
Last Service Date | Last Serviced |
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 = In Service — so crews aren't scrolling past disposed or off-hired equipment in dropdown fields
Re-sync from scratch: Use this after a bulk asset restructure or for the initial clean load
Prerequisites
Flowsite Premium or Platinum plan
A Microsoft (Dataverse) connection set up in Flowsite
A Dashpivot Plant & Equipment list already created (the flow populates it — it doesn't create it)
Frequently Asked Questions
What happens to assets that are disposed of or off-hired?
When an asset is removed or deactivated in Dataverse, the corresponding row is archived in the Dashpivot list — not permanently deleted. This means historical pre-starts, inspections, and maintenance records that reference that asset stay intact.
Can I exclude decommissioned or off-hired equipment from showing in forms?
Yes. Use the optional row filter on the flow to set a condition such as Status = In Service. Only assets matching that condition will sync, so disposed or off-hired equipment won't appear in dropdown fields.
Does this work with Dynamics 365 Field Service?
Yes. Dynamics 365 Field Service stores asset data in Dataverse tables. As long as your asset records are accessible as a Dataverse table in your Power Apps environment, Flowsite can sync them into Dashpivot.
Will updating an asset's status or location in Dataverse update it in Dashpivot too?
Yes. Each scheduled sync picks up updated rows from Dataverse and reflects those changes in the Dashpivot Plant & Equipment list automatically.
Do new assets appear in Dashpivot automatically?
Yes. Any new asset added in Dataverse will appear in the Dashpivot Plant & Equipment list at the next scheduled sync. No manual upload or CSV re-import is needed.