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.
I have a matrix visualization with two dimension fields, Category and Metric. For each Category, there can be different Metrics (or subcategory). I am attempting to calculate custom subtotal values to display on rows in matrix, but having issues in returning a value at the Category level. For this special Category row value, "Monthly_Actual to Number Measure", won't return for some reason. I will say that it is a measure from a different table ('bsc_outcome') whereas the other measure is coming from the 'Union_Table'. I replaced this value with a different value from 'Uniton_Table' to test and it worked, so it has something to do with table relationship or filters? Not sure. See image and dax calculation below:
Matrix Value for Category Test v2 =
Thank you!!!
Solved! Go to Solution.
@Amar_Kumar Thank you! I experimented a little bit and while that formula didn't quite work, this one seemed to do the trick:
@Amar_Kumar Thank you! I experimented a little bit and while that formula didn't quite work, this one seemed to do the trick:
This is a filter / relationship issue, not an ISINSCOPE issue.
Your matrix uses Category and Metric from UnionTable.
At the Category subtotal level, the filter on UnionTable[Category] does not propagate to bsc_outcome, so [Monthly_Actual to Number Measure] evaluates to blank. That’s why measures from UnionTable work but the one from bsc_outcome does not.
Quick fix is to force the Category filter onto bsc_outcome:
Matrix Value for Category Test v2 =
SWITCH(
TRUE(),
ISINSCOPE(UnionTable[Metric]),
[Current Month],
ISINSCOPE(UnionTable[Category]),
CALCULATE(
[Monthly_Actual to Number Measure],
TREATAS(
VALUES(UnionTable[Category]),
bsc_outcome[Category]
)
),
BLANK()
)Root cause is either:
No active relationship between UnionTable and bsc_outcome
Category does not filter bsc_outcome
Relationship direction is wrong
Fixing the model relationship can also solve it without TREATAS.
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 |
|---|---|
| 32 | |
| 24 | |
| 22 | |
| 22 | |
| 13 |
| User | Count |
|---|---|
| 61 | |
| 47 | |
| 27 | |
| 24 | |
| 19 |