Need the ability to create multiple relationships between table pairs. Example: Dynamics GP - SOP Sales Transactions and Sales Line Items have to be joined by SOP Type AND by SOP Number.
18 Comments
- 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'.
- This looks the same as https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/9115396-multiple-relationships-for-crm
- Is a pain that Power BI don't support multiple relationships between tables, is a mistake!
- 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
- It'd be nice, but a simple alternative is to create another column on the dataset that concatenates fields to create a compound key.
- 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....
- 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.
- I don't understand why this isn't already supported. Even Access allows joining on multiple primary keys.
- This is a major point of frustration for me. Too often I would need to join on 3 or four columns, adding new columns as a workaround is just frustrating and unnecessary. Also, I don't want them in the same table, so merging the tables in the query editor is useless.
- I've encountered numerous situations where this would have been needed as there are e.g. multiple roles between a transaction table and an entity table. This becomes specially crucial if the entity instances (e.g. Departments) are part of a hierarchy you need to be able to filter by using a higher level common nominator (e.g. Business Unit) and any of the related departments separately -- this an actual business case unsolvable by hierarchy model supported by Power BI :( I've actually have had PowerBI disqualified by the end users due to this limitation in few occasions, simply making copies of the large and complex hierarchies to server few different roles isn't simply going to cut it, end users want to pick the hierarchy level from one simple selection.
