This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Hello,
I have a problem when i Want to filter my Matrix.
This is the matrix i have:
The column "__days left" is a measure: __days left =
var __all sub = CALCULATE (SELECTEDVALUE(Tabelle22[Days left]), FILTER(Tabelle22, NOT(ISBLANK(Tabelle22[Level3]))))
var all tasks = CALCULATE (SUM(Tabelle22[Days left]), FILTER(Tabelle22, ISBLANK(Tabelle22[Level3])), REMOVEFILTERS (Tabelle22[Level3]))
Hi @kathrin_44,
Thank you for sharing your question! This is a known limitation when filtering a matrix visual by a DAX measure, especially one that uses ISINSCOPE. When rows are collapsed in a hierarchy, Power BI evaluates the measure at the parent level, which can cause unexpected behavior with filters.
Here are a few things you can try:
1. Use a visual-level filter on the measure: In the Filters pane, drag the __days left measure to the "Filters on this visual" section and set your condition. Note that this filters at the row level that is currently visible, not at sub-task level when collapsed.
2. Add a calculated column instead: If you need to filter on a fixed numeric value, consider creating a calculated column in your table and use that as your filter. Calculated columns are evaluated row by row at import time and filter more reliably.
3. Use CALCULATE with REMOVEFILTERS: If you want sub-tasks to be visible based on their days-left value even when collapsed, consider restructuring your measure to propagate the filter context down to the lowest level.
Could you clarify what filtering behavior exactly you expect — for example, should rows disappear from the matrix when days left = 0, or should they simply show 0?
Hope this helps!
Hi @kathrin_44,
Thank you for sharing your question! This is a known limitation when filtering a matrix visual by a DAX measure, especially one that uses ISINSCOPE. When rows are collapsed in a hierarchy, Power BI evaluates the measure at the parent level, which can cause unexpected behavior with filters.
Here are a few things you can try:
1. Use a visual-level filter on the measure: In the Filters pane, drag the __days left measure to the "Filters on this visual" section and set your condition. Note that this filters at the row level that is currently visible, not at sub-task level when collapsed.
2. Add a calculated column instead: If you need to filter on a fixed numeric value, consider creating a calculated column in your table and use that as your filter. Calculated columns are evaluated row by row at import time and filter more reliably.
3. Use CALCULATE with REMOVEFILTERS: If you want sub-tasks to be visible based on their days-left value even when collapsed, consider restructuring your measure to propagate the filter context down to the lowest level.
Could you clarify what filtering behavior exactly you expect — for example, should rows disappear from the matrix when days left = 0, or should they simply show 0?
Hope this helps!
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 26 | |
| 25 | |
| 24 | |
| 21 | |
| 14 |
| User | Count |
|---|---|
| 56 | |
| 50 | |
| 26 | |
| 19 | |
| 18 |