From Spreadsheets to Dataverse: A Field App Blueprint for Construction Teams
By Radhika P. ·
How a builder running 40+ communities on separate spreadsheets moved to Dataverse and a Power Apps Canvas field app: the architecture, three hard lessons, and a phased MVP plan you can reuse in any industry.
A construction company I worked with ran its entire operation on spreadsheets. Moving that operation to Power Apps and Dataverse changed how the field, the office and leadership shared information. This post covers the architecture, the lessons, and a phased plan you can reuse in almost any industry.
The problem: forty spreadsheets, three versions of "done"
The builder had more than 40 active communities running at once, and each community had its own spreadsheet with no shared format. Each product type (single-family, townhome, amenity buildings) carried more than 570 milestones and tasks. Milestones are real construction phases such as Construction Start, Framing, Drywall, Certificate of Occupancy and Closeout, with a task list under each one.
Scheduling, accounting and field updates lived in separate tools. On site, information lived on clipboards, in texted photos and in conversations at the trailer. Updates took two to three days to reach leadership.
The real pain was this: the field, the office and leadership were each working from a different version of what "done" meant. Nobody was doing anything wrong. They just did not share the same picture.
Why Power Platform
The options were custom software, a vendor tool, or Power Platform.
- Speed: custom software means months before anyone sees a screen. A vendor tool is quick to buy but rarely fits your process. Power Platform lands in between, usable in weeks.
- Cost: custom means a dev team indefinitely, and a vendor tool means per-seat fees that grow. Power Platform was often already covered by existing Microsoft 365 licensing, so check what you already have before assuming a new cost.
- Data ownership: with Power Platform the data sits in your own tenant from day one.
- Room to grow: you can add a Canvas app, a dashboard or a portal on the same data without a rebuild.
The architecture in four layers
Platform. Separate dev, test and prod environments, with SharePoint for documents, Teams for project channels, and Entra ID plus data loss prevention policies for guardrails.
Data. Dataverse holds Project, Building, Milestone and Task as one shared source of truth, linked by lookups instead of typed names. Security roles control who sees which rows, and business rules handle roll-ups and defaults.
Automation. Four Power Automate flows do the busywork: Generate (builds the task list when a building is created), Notify, Sync and Version.
Experience. A Model-Driven app for the office, a Canvas app for field crews on iPads, a Power BI dashboard for leadership, and a Power Pages portal where subcontractors see only their own work.
The data difference
In a spreadsheet, "Oakridge" and "Oak Ridge" are two communities, and "Started" and "In progress" are two statuses. In Dataverse, Building is a lookup to a real record, and Status is a Choice column, so people pick from a fixed list instead of typing. [1] Every row also records who changed it and when, which answers "who decided this?" without a conversation at the trailer.
The field app: three taps, gloves on
The Canvas app was designed screen by screen for a job site:
- Buildings: pick a building and see progress next to each one, for example three of eight milestones done.
- Milestones: status is a color, not a dropdown: gray is not applicable, red not started, yellow in progress, green done. The whole row is the tap target.
- Status and notes: big buttons that work with gloves on, a camera to attach a photo to the milestone, and a note logged with who and when.
There is also an English/Spanish toggle that switches every label instantly. The app translates its own labels, not what a person typed, so a note stays exactly as written.
Three lessons I would apply again
1. Lock the data model before you build screens. We changed the data structure after version one was live, which meant reworking both the app and the flows. It was painful and avoidable.
2. Standardize choice values across office and field. If one team enters "In Progress" and another enters "Started", your reports quietly stop being accurate.
3. Plan for bad signal and failed flows from day one. Job sites have patchy connectivity, so cache data locally and sync when back online. In flows, wrap risky steps in a try/catch/finally pattern using scopes so one bad record does not take down the whole batch. [2]
Two decisions worth repeating: give the office a Model-Driven app and the field a Canvas app, and keep templates separate from live project data so you can change the standard plan without rewriting running projects.
A realistic MVP roadmap
You do not need all of this on day one.
- Weeks 1 to 3: stand up the Dataverse data model, load the standard milestone templates and give the office a Model-Driven app. Retire the worst spreadsheet first.
- Weeks 4 to 6: ship the Canvas field app, then add the Generate and Notify flows so status moves from paper to same-day.
- Month 2 and beyond: add the Power BI dashboard, a subcontractor portal, and harden environments and security as more communities come on.
Earn the right to build the dashboard by getting the shared data and the field app right first. Projects that start with the dashboard often end up with a pretty view over messy data.
What success looks like
The architecture described here is real and I built it. The before-and-after below is the typical shape of this kind of change, not a verified scorecard for one client:
- Before: dozens of spreadsheets, status that arrives days late, and leadership learning about a slip at the monthly review.
- After: one shared plan, same-day status, and a standard plan that scales to the next community instead of starting from a blank spreadsheet.
The payoff still depends on adoption. A solid app that nobody uses delivers nothing, so plan rollout and training alongside the build.
Takeaway
You don't pour the roof before the foundation. Start with one process, ship something small, and keep building up. If you can swap "building, milestone, task" for your own hierarchy, the same pattern works for your industry.
Sources
- ↑ Choice columns and formulas in canvas apps – Microsoft Learn (2026) · learn.microsoft.com
- ↑ Use scopes to organize actions in cloud flows – Microsoft Learn (2026) · learn.microsoft.com
FAQ
Why use Dataverse instead of SharePoint lists or SQL?
SharePoint lists struggle with this scale and relationship complexity. SQL needs you to build your own security and app layers. Dataverse gives relational tables, row-level security and business rules, wired into Power Platform.
Why a Canvas app for the field instead of Model-Driven?
Canvas lets you design exactly for big touch targets and a simple flow on an iPad. A Model-Driven app suits office staff who manage many records at a desk.
Do I need to code to build this?
Not to start. Canvas apps and Power Automate are largely low-code. Coding helps for custom needs such as JavaScript web resources, plugins or advanced Power Fx formulas.
What happens when a Power Automate flow fails?
Wrap risky steps in scopes configured as try, catch and finally. Failures are logged and handled gracefully instead of failing silently or leaving half-updated records.
How do subcontractors see only their own data?
Dataverse security roles scope access at the row level. Data outside a subcontractor's scope is not available to them at all, rather than being hidden in a filtered view.
How long does an MVP take?
A core data model plus office app is usually a few weeks once the structure is locked. The field app and flows add more time, depending on how many flows you need.