Forum Discussion
Data modeling and report structure
ldrysdale13 , if you want to deal with these 5 using role-playing dimension then refer to this - https://radacad.com/userelationship-or-role-playing-dimension-dealing-with-inactive-relationships-in-power-bi
You can create a common table like
distinct(union(distinct(table[Horizontal Lead/PM]), distinct(table[Design]), distinct(table[Plan Production]), distinct(table[Stormwater/Support]), distinct(table[Landscape Architecture]), distinct(table[LA support])))
Star schema is best. You can take out few dimension from this table - https://www.sqlbi.com/articles/the-importance-of-star-schemas-in-power-bi/
In this series, in the first few videos( 2 and 3rd), I have broken a single table into the star
https://www.youtube.com/watch?v=kU2M1LmNvNo&list=PLPaNVDMhUXGaaqV92SBD5X2hk3TMNlHhb&index=2
Thank you for your response. I tried to use the role-playing dimension and created separate tables from my original table for each category. I also pulled in an Employee fact table that has a relationship to each category table through Employee Name. This seems to work OK from an overall employee/category standpoint, but I am struggling on how to also incorporate the Project related information. I also created a project fact table from my original table but struggling on how to also get the correct project data (specifically project number) into my visuals.