Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Hi,
I would like my dashboard to have the option to select specific values from one table, based on the relationship with the other table. The problem is that in the table that the filter is supposed to go after, the keywords in some rows occur after a comma:
Filter table:
ID | Description |
CS1.01 | .... |
.... | .... |
CS1.10 | .... |
CS2.01 | .... |
.... | ... |
CS6.10 | .... |
The table by which I want to filter
ID | Name | Price | CODE |
1 | .... | .... | CS2.05, CS2.07 |
2 | .... | .... | CS1.01, CS1.02, CS1.04, CS1.04, CS1.05, CS1.06, CS1.07, CS1.08, CS1.09, CS2.03 |
3 | .... | .... | CS2.01 |
.... | .... | .... | CS3.10, CS5.05 |
45 | .... | .... | CS4.08, CS5.04, CS5.09 |
Is it possible that by selecting an item such e.g. CS1.05 in the first table, I will get all the rows containing this code from the second table, or is the data badly designed?
Thanks for help!
Alleckii
Solved! Go to Solution.
I found the solution that helps me.
Creating a slicer that filters multiple columns in Power BI by SQLBI
I found the solution that helps me.
Creating a slicer that filters multiple columns in Power BI by SQLBI
@alleckii Ha! I missed that, you don't need to create a relationship but you can use the solution provided in one of my 1st videos here. https://youtu.be/zS1IDl3DLak
I would ❤ Kudos if my solution helped. 👉 If you can spend time posting the question, you can also make effort to give Kudos to whoever helped to solve your problem. It is a token of appreciation!
⚡ Visit us at https://perytus.com, your one-stop shop for Power BI-related projects/training/consultancy.
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.
@alleckii the best practice would be to split your table by comma on rows in PQ and then you don't need to anything extra and it should work.
I would ❤ Kudos if my solution helped. 👉 If you can spend time posting the question, you can also make effort to give Kudos to whoever helped to solve your problem. It is a token of appreciation!
⚡ Visit us at https://perytus.com, your one-stop shop for Power BI-related projects/training/consultancy.
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.
@parry2k Are You sure thath will work? I tried to do it this way, but the relationship between the tables did not allow to select after several columns. When I wanted to select CS1.01, only the rows that had this code in the column followed by the active relationship with the first table were selected.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Ask questions in Eventhouse and KQL, Eventstream, and Reflex.
User | Count |
---|---|
84 | |
83 | |
64 | |
61 | |
55 |
User | Count |
---|---|
171 | |
109 | |
109 | |
73 | |
71 |