Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Hi community,
please help me with the issue I'm facing.
I have a table with items (ID, description). There is one item that was created twice by mistake, once normal and once with one space as the last character of ID. Because of that pair of ID's model is creating many to many relationship. It seems like ending space is ignored while checking the type of relashionship. Is this a bug or am I missing something?
I don't want to remove either of the ID's as in real it is not duplicate value.
I would appreciate any help.
Item IDDescription
1A | Item 1 |
1A | Item 1 with space |
2A | Item 2 |
3B | Item3 |
DateItem IDQuantity
15.01.2023 | 1A | 10 |
15.01.2023 | 1A | 12 |
15.01.2023 | 1A | 15 |
15.01.2023 | 3B | 20 |
16.01.2023 | 1A | -5 |
16.01.2023 | 1A | -3 |
16.01.2023 | 1A | 6 |
16.01.2023 | 2A | 5 |
16.01.2023 | 2A | 4 |
Regards,
Solved! Go to Solution.
Hey!
Simple but annoying answer to this one.
If the relationship is based on item ID then it will be a many to many relationship
(something we want to avoid at all costs in Power BI 😭)
The fix to this will be to create a relationship that is based on a unique item in one list to many in another.
For example, you could add a index column into your { ItemID, Description } table and then merge this into your { Date, ItemID, Quantity } table. You would then be able to create a one-to-many realtionship based on this index.
Appreciate your Kudos!
Please accept the solution if it answers your question 🙂
So it is a bug? Good to know. And thank you for your post. It solves the issue.
No Problem at all!
It's not a bug, just the way Power BI operates unfortunately 🙁
Appreciate your Kudos!
Please accept the solution if it answers your question 🙂
Hey!
Simple but annoying answer to this one.
If the relationship is based on item ID then it will be a many to many relationship
(something we want to avoid at all costs in Power BI 😭)
The fix to this will be to create a relationship that is based on a unique item in one list to many in another.
For example, you could add a index column into your { ItemID, Description } table and then merge this into your { Date, ItemID, Quantity } table. You would then be able to create a one-to-many realtionship based on this index.
Appreciate your Kudos!
Please accept the solution if it answers your question 🙂
User | Count |
---|---|
141 | |
113 | |
104 | |
78 | |
64 |
User | Count |
---|---|
136 | |
125 | |
107 | |
70 | |
61 |