Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
Hi,
I'm having the following question regarding model design:
In typical organizations, you find that multiple areas exist, such as 'finance', 'hr', or 'production'. Since the advice from Microsoft is to keep models as small as possible (https://learn.microsoft.com/en-us/training/modules/design-model-power-bi/1-introduction), this would lead to the conclusion to split up the data for these business areas, and to offer split-up models for each of them. However, this seems to conflict with the goal of keeping a single source of truth (f.e. https://powerbi.microsoft.com/nl-nl/blog/cerner-corporation-the-importance-of-a-single-source-of-tru...), as this would cause duplication of Power Query Editor steps and duplications in definitions of DAX measures for tables that are part of more than 1 model.
How can these seemingly conflicting goals best be reconciled? Can we for example find a way to avoid duplication of steps and measures, thereby safeguarding the existence of a single source of truth?
Thanks.
The Power BI Data Visualization World Championships is back! It's time to submit your entry.
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 61 | |
| 48 | |
| 35 | |
| 25 | |
| 23 |
| User | Count |
|---|---|
| 134 | |
| 110 | |
| 59 | |
| 39 | |
| 32 |