- Comments (17)
- Merged Idea (2)
RE: Add the ability for multiple relationships between table pairs
I totally agree - this is a competitive disadvantage in the Microsoft BI stack today. Creating artificial keys could introduce unintended problems, not to mention it's non-value-added time and extra data to haul around.
RE: Add the ability for multiple relationships between table pairs
It'd be nice, but a simple alternative is to create another column on the dataset that concatenates fields to create a compound key.
RE: Add the ability for multiple relationships between table pairs
Really guys this is a big shortcoming to let linger for like 2 years +. THere currently is no practical ways (other than writing & maintaining tons of replace queries) to switch values that are inputed into different labels for the dashboard, in case your source data isn't presentable directly/unformatted.
It would be sooooooooo simple to do that with a single value & labels lookup table, that would be referred to by each column from the data that are used to create the graph in the dashboard.
But not. You either have to create (and maintain) a bizzilion extra tables, or write a bunch of queries.... Please power bi....
RE: Add the ability for multiple relationships between table pairs
Very valuable! Also vote on other similar ideas: https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/9196284-use-composite-joins-in-manage-relationships-setup
and
https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/10321815-composite-key-support-in-power-bi
RE: Add the ability for multiple relationships between table pairs
Is a pain that Power BI don't support multiple relationships between tables, is a mistake!
RE: Add the ability for multiple relationships between table pairs
This looks the same as https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/9115396-multiple-relationships-for-crm
RE: Add the ability for multiple relationships between table pairs
This would be very valuable for models that have foreign keys for example:
Tickets that have many users using CreatedById -> UserId. As alias 'Creator' That is the default association.
Tickets that have many users using AssignedToId -> UserId. As alias 'Worker'.
Tickets that have many users using UpdatedById -> UserId as alias 'Editor'.