Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
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.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
User | Count |
---|---|
126 | |
78 | |
78 | |
59 | |
51 |
User | Count |
---|---|
164 | |
84 | |
68 | |
68 | |
58 |