Projects · Professional Project
Enterprise Power Platform & Dataverse Architecture
CVO SemperJanuary – June 2025 (6 months)Remote / Meise, Belgium
Test draft, the real story is coming soon. An architectural proof of concept that tested whether Microsoft Dataverse and Power Platform Dataflows could carry the organisation's relational data, automated imports and business logic, and what that would mean for licensing and governance.
Test draft: this page is a placeholder for trying out detail pages. The text, table and diagram are examples, not the real story yet. Real content coming soon™.
The question
The organisation's data lived in several separate places. The aim of this proof of concept (PoC) was to find out whether a relational model in Dataverse, filled automatically by Dataflows, would be a sound basis for future Power Apps, and what it would cost in licences and governance.
The approach
- Relational data modelling: entity-relationship structures, custom tables, automated lookup fields and roll-up calculations in Dataverse.
- Automated Dataflows (ETL): native Power Platform Dataflows in Power Query Online extract and transform the data, and fill the Dataverse tables automatically, without Power Automate.
- Architecture and governance evaluation: a strategic look at licensing and governance before any rollout.
The outcome
| Aspect | Finding |
|---|---|
| Data model | Relational structures, lookups and roll-ups worked as intended |
| Data imports | Dataflows filled the tables automatically, independently of Power Automate |
| Production | The evaluation laid the foundation for later production rollouts on structured SharePoint Online backends |
What would you do differently next time? A short reflection works well here.
What I learned
Use this section for the lessons you'd take into the next project.