2 source-controlled
Semantic models
Governed Power BI models for operational and financial reporting
BI delivery and ERP-connected reporting Internal work sample
Delivered two Power BI data models across 128 entities for operational and financial reporting. Their definitions are kept under version control so changes can be reviewed.
-
The problem
Operational and financial reports lacked governed models, making changes difficult to review and prone to drift.
-
My role
Authored eight calculated columns and thirty-three measures for reconciliation, variance and many-to-many bridging.
-
Where it stands
Two governed semantic models — eight calculated columns and thirty-three measures over a roughly thirty-five-table financial star across 128 entities — delivered under a repeatable, source-controlled process.
Results and evidence
~35 tables
Financial star
33
DAX measures
plus 8 calculated columns
128
Entities served
Business impact
Replaces drifting reports with a governed, reviewable foundation.
How I did it
- 01
Structured the financial model as a conformed star of roughly thirty-five tables.
- 02
Kept both models under source control and verified edits against a written pre-flight checklist.
Tools and working context
Two Power BI semantic models over group data spanning 128 entities; one operational (PMO), one financial.
- Tools
- TMDL v3 / PBIP · DAX · Power Query (M) · Dynamics 365 CDS
- Business area
- BI delivery · Group reporting
- Skill type
- BI · Data & Reporting
Why I made these choices
- Used source-controlled TMDL so model changes are reviewable and diffable.
- Required a pre-edit check to prevent load-breaking errors.
Skills used
- DAX Data & Reporting Strong
- TMDL semantic modelling Data & Reporting Strong
What I learned
- Source control and a pre-flight gate make semantic-model editing repeatable.
What comes next
- Complete the financial-star refactor and publish a reusable measure library.