Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hi there,
I'm new to Power BI Desktop so I'm presuming that (1) I don't understand how it should work or (2) it's still just a new product and this issue will be improved later.
I am learning Power BI by creating visualizations with my Helpdesk data. The data is coming from Excel and I have a Tickets table and a Users table. Each ticket has multiple foreign key references to Users because each ticket has an assignee, a submitter, and a requester (among other similar fields) which are all defined in Users.
The problem is that I can only make one relationship between one of the fields in Tickets and Users.
Is there a specific reason for this behavior?
I did find a workaround by using Merge Queries but I think a relationship is more logical (or, at least, I'm more used to that kind of thinking.)
Thanks!
Solved! Go to Solution.
Easiest way around this is to import your Users table multiple times, Assignee table, Submitter table and Requester table, etc. and create the relationships between the appropriate fields to the appropriate user table. Same exact query, just change the name.
You can create multiple relationships between tables but only one of them would be active. In case of multiple relationships, you would need to specify which one to be used when creating report visual. Currently we do not support this capability and always use the active relationship.
Using Query View to create a single merged table is a proper workaround. Supporting multiple relationships is in our backlog. Feel free to add your vote in the forum: https://support.powerbi.com/forums/265200-power-bi
Thanks,
Alex.
Easiest way around this is to import your Users table multiple times, Assignee table, Submitter table and Requester table, etc. and create the relationships between the appropriate fields to the appropriate user table. Same exact query, just change the name.
Interesting idea. I'll give it a shot.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
74 | |
73 | |
56 | |
38 | |
31 |
User | Count |
---|---|
84 | |
63 | |
63 | |
49 | |
45 |