Filtering Data challenge

[Daniel564]

Hello community!

I have a challenge i can't solve alone. I have a database like you see on the picture, and i should create a filter button for the Location, which filters for all contracts from the selected Location and gives as the result all rows, in which the Contractnumbers from the selected Location are in.
For Example you select Paris in the filter, the result would be as shown in the graphic, because the both Paris rows are from the selected Location and Berlin and London have the same Contractnumbers, so they shuold also be displayed.
Thank you for your thoughts!

[Daniel564]

Thanks to all for the comments. The Solution with the additional measure is working 🙂 

Have a great day!

[v-karpurapud]

Hi @Daniel564 

We have not received a response from you regarding the query and were following up to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank You.

[v-karpurapud]

Hi @Daniel564 

Thanks for reaching out to the Microsoft fabric community forum. 

I would also take a moment to thank  @lbendlin  and @ArwaAldoud , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

I hope the shared details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you 

Best Regards, 
Community Support Team .

[lbendlin · Accepted solution]

use a measure as a visual filter.

[ArwaAldoud]

Hi @lbendlin 

I actually tried a similar DAX approach, but the main difference is that you separated the Location into its own table that’s a smart move to simplify the filtering logic.
Thanks for sharing

[lbendlin]

This is a mandatory design, not a "smart move to simplify".  The request can only be fulfilled with disconnected tables.

[ArwaAldoud]

I’m fully aware that a disconnected table is the typical design pattern — my approach was more of an experiment to validate if it could work directly within the main table.
It’s interesting how exploring such variations helps clarify why certain designs are “mandatory.”