Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I have three data tables that look like this:
I have many visuals/charts/tables that center around ItemTable and use ItemTable as a filter.
Right now, I have ItemTable related directly ProblemLog by Item -- so if I filter to A1 from ItemTable, I just see Problem #1. This is a 1:Many relationship (can have multiple problems for one item).
The challenge I have is taking into account the ParentChild table. When I filter ItemTable to A1, I'd like to see the Problems for A1 and all of its children. So when filtering for A1, I need to see Problem #1 and Problem #3, because D4 is a child of A1.
Does anyone have a thought on how to set up relationships with the ParentChild table?
It's almost like I need the relationships set up like this, though I don't think this would actually work since there can only be one active relationship:
Solved! Go to Solution.
Update, solved this, here's the simplified solution for anyone searching in the future:
I manipulated my ParentChild table to take this format, then was able to relate ItemTable to ParentChild to ProblemLog.
@Anonymous Check the attached solution.
I would 💖 Kudos 🙂 if my solution helped. 👉 If you can spend time posting the question, you can also make efforts to give Kudos whoever helped to solve your problem. It is a token of appreciation!
Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!
Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo
If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤
Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.
@Anonymous Check the attached solution.
I would 💖 Kudos 🙂 if my solution helped. 👉 If you can spend time posting the question, you can also make efforts to give Kudos whoever helped to solve your problem. It is a token of appreciation!
Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!
Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo
If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤
Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.
Hi @parry2k -- thanks, this is the almost exact approach I used.
I actually created 4 separate queries for each "child" level and then appended the four together -- using Unpivot is much better! THANK YOU!
Update, solved this, here's the simplified solution for anyone searching in the future:
I manipulated my ParentChild table to take this format, then was able to relate ItemTable to ParentChild to ProblemLog.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
114 | |
100 | |
83 | |
70 | |
61 |
User | Count |
---|---|
149 | |
114 | |
107 | |
89 | |
67 |