Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Hello guru's,
I know I have done something wrong and am looking for advice. I'm guessing with the proper design both issues can be resolved. I currently have two problems:
1) When there are two employees in a [Project List] column, the report visualization value is shown as blank.
2) I have copied the [Employee List] query multiple times so I have 3 in total so I can create 3 different relationships (one for each column talked about below). I know this is bad form, data set is very small and is proof of concept.
Simplifying... I have two tables (source is sharepoint online):
1) [Projects]
2) [Employees]
In [Projects] I have 3 columns:
1) [Projects] \ Manager
2) [Projects] \ Lead(s) - can have many values
3) [Projects] \ Tech(s) - can have many values
These Leads and Techs columns contain a comma seperated list of employee ID's (a whole #) that link up with the [Employees] table where their name is stored.
On my report, I'd like to display all employee names for each project. Open to different methods.
[Projects] Table
Project Name | Manager | Leads | Techs |
Install Windows 3.1 | 1 | 2 | 3,4 |
Employees Table
Employee ID | Name |
1 | Bill Gates |
2 | Bill Gates Jr |
3 | Golden Gates |
4 | Triomphe Gates |
I've watched this youtube video but can't quite see how to apply it in my scenario:
Handling MULTIPLE fact tables in Power BI - YouTube
Thanks, any advice is really appreciated.
Solved! Go to Solution.
HI @drewP76,
First, I do not so recommend you to merge multiple id in the same field. (power bi not able to recognize and mapping it with detailed records)
I'd like to suggest you create a expand table to expand the project table to project, attribute and value. (project id, role type, employee id) Then you can use this to link project table and fact table employees.
For multiple fact table relationships, perhaps you can take a look at the following document to design the star schema relationship that power bi works effectively.
Understand star schema and the importance for Power BI - Power BI | Microsoft Docs
Regards,
Xiaoxin Sheng
HI @drewP76,
First, I do not so recommend you to merge multiple id in the same field. (power bi not able to recognize and mapping it with detailed records)
I'd like to suggest you create a expand table to expand the project table to project, attribute and value. (project id, role type, employee id) Then you can use this to link project table and fact table employees.
For multiple fact table relationships, perhaps you can take a look at the following document to design the star schema relationship that power bi works effectively.
Understand star schema and the importance for Power BI - Power BI | Microsoft Docs
Regards,
Xiaoxin Sheng
User | Count |
---|---|
86 | |
82 | |
68 | |
64 | |
55 |
User | Count |
---|---|
123 | |
100 | |
90 | |
83 | |
66 |