Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now
Solved! Go to Solution.
There are many good courses on data modeling in Power BI. Here's one of them (I have no affiliation to PluralSight, I just sometimes use their services):
PluralSight Course on Data Modeling in Power BI
There is also a course on data modeling (and DAX) at www.sqlbi.com. Again, I'm not affiliated with them but have gone through their courses.
Basics are these:
1. You should always aim for the STAR SCHEMA, that is, your fact table should be surrounded with dimensions that join to your fact table in a 1-to-many fashion. Your fact table should only store metrics (numbers) and keys to your dimensions. It's best to hide all the columns of your fact table so that only measures defined in it are visible to the end user and slicing is done by selecting attributes from dimensions. Fact tables should not store row identifiers but dimensions must.
2. You should always have proper Date Tables.
3. You should never join 2 fact tables directly. They can and should be joined via dimensions.
4. You should aim for a model where the number of distinct values in a column is small.
5. You should always start with 1-to-many relationships and use the other types only when you fully understand the implications for your model and calculations. If you don't, then be prepared to see things which will be inexplicable (to you).
As for your last question.... Yes, if you have many similar files, you should consolidate them into one entity and load int Power BI. Use Power Query to massage the data into the STAR SCHEMA model.
Best
Darek
Hi.
Well, maybe you just can't get anywhere because instead of creating a proper data model you are trying to cut corners with a model that sucks? This often happens... A good model must have a proper data table that is designated as such (there is an option on the ribbon that lets you mark a table as date table). Please, first build a correct model and then make a screenshot of the relationships. Then make a screenshot of the matrix with all the slicers and what have you... and then, and only then, I could help you. The more info about your model you include, the better the chance that someone will actually find an answer to your question.
Thanks!
Best
Darek
There are many good courses on data modeling in Power BI. Here's one of them (I have no affiliation to PluralSight, I just sometimes use their services):
PluralSight Course on Data Modeling in Power BI
There is also a course on data modeling (and DAX) at www.sqlbi.com. Again, I'm not affiliated with them but have gone through their courses.
Basics are these:
1. You should always aim for the STAR SCHEMA, that is, your fact table should be surrounded with dimensions that join to your fact table in a 1-to-many fashion. Your fact table should only store metrics (numbers) and keys to your dimensions. It's best to hide all the columns of your fact table so that only measures defined in it are visible to the end user and slicing is done by selecting attributes from dimensions. Fact tables should not store row identifiers but dimensions must.
2. You should always have proper Date Tables.
3. You should never join 2 fact tables directly. They can and should be joined via dimensions.
4. You should aim for a model where the number of distinct values in a column is small.
5. You should always start with 1-to-many relationships and use the other types only when you fully understand the implications for your model and calculations. If you don't, then be prepared to see things which will be inexplicable (to you).
As for your last question.... Yes, if you have many similar files, you should consolidate them into one entity and load int Power BI. Use Power Query to massage the data into the STAR SCHEMA model.
Best
Darek
Check out the October 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
33 | |
16 | |
13 | |
10 | |
8 |
User | Count |
---|---|
59 | |
20 | |
12 | |
11 | |
10 |