Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi all, I have been using Power BI in a medium sized company for about 2 years now. I have created many good dashboards and have mostly taught myself. I used to work with Transact SQL and create visuals in an ERP through creating views in SQL and using the views as my data source, so grouping, merging etc always took place in SQL. The company I work for now works with a PSA system using an API. I often work with multiple fact tables. I have read a lot that it's best to create a star schema, but I still find it easiest to merge the tables in Power Query and expand only the needed columns to have all my data in 1 table. Is this bad modeling? The data isn't huge, but I want to become better so would like to have some comments.
Solved! Go to Solution.
@BellPower , When you need a measure that needs to go across rows, you should use the ALL function or time intelligence functions. This approach works best with a star schema. While it may work for smaller datasets, for complex problem solving, always use a star schema with a proper date/calendar table.
refer video from Guyinacube- https://www.youtube.com/watch?v=vZndrBBPiQc
@BellPower , When you need a measure that needs to go across rows, you should use the ALL function or time intelligence functions. This approach works best with a star schema. While it may work for smaller datasets, for complex problem solving, always use a star schema with a proper date/calendar table.
refer video from Guyinacube- https://www.youtube.com/watch?v=vZndrBBPiQc
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
69 | |
68 | |
40 | |
29 | |
26 |
User | Count |
---|---|
86 | |
49 | |
45 | |
38 | |
37 |