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.
Solved! Go to Solution.
Hi @tberr86
As you've rightly said, RELATED is not required here. RELATED requires a row context which does not exist in a measure (unless introduced within the measure by an iterator). In any case, filters applied to tables on the 1-side of a 1:many relationship automatically "propogate" from the 1-side to the many-side table.
I would also suggest CALCULATE ( COUNTROWS (...) ) rather than COUNTROWS ( CALCULATETABLE (...) )
Also, since the "Q75" filter is common to both components of the measure, you could use an outer CALCULATE with that filter applied, and place the remaining filters within nested CALCULATE calls.
Putting all this together, you could write something like this:
Total WIP =
CALCULATE (
VAR ActiveWIP =
CALCULATE (
COUNTROWS ( 'SCHEDHOUSEDETAIL' ),
ISBLANK ( 'SCHEDHOUSEDETAIL'[actualfinishdate] )
)
VAR UnsoldCompletedHomes =
CALCULATE (
COUNTROWS ( 'SCHEDHOUSEDETAIL' ),
NOT ISBLANK ( 'SCHEDHOUSEDETAIL'[actualfinishdate] ),
ISBLANK ( 'HOUSE MASTER'[contract_date] ),
NOT ISBLANK ( 'HOUSE MASTER'[Start Date] )
)
RETURN
ActiveWIP + UnsoldCompletedHomes,
'SCHEDHOUSEDETAIL'[activitycode] = "Q75"
)
Alternatively, you could create two separate measures for ActiveWIP and UnsoldCompleteHomes, and sum them in the Total WIP.
Does the above measure give the expected result?
Regards,
Owen
Hi @tberr86
As you've rightly said, RELATED is not required here. RELATED requires a row context which does not exist in a measure (unless introduced within the measure by an iterator). In any case, filters applied to tables on the 1-side of a 1:many relationship automatically "propogate" from the 1-side to the many-side table.
I would also suggest CALCULATE ( COUNTROWS (...) ) rather than COUNTROWS ( CALCULATETABLE (...) )
Also, since the "Q75" filter is common to both components of the measure, you could use an outer CALCULATE with that filter applied, and place the remaining filters within nested CALCULATE calls.
Putting all this together, you could write something like this:
Total WIP =
CALCULATE (
VAR ActiveWIP =
CALCULATE (
COUNTROWS ( 'SCHEDHOUSEDETAIL' ),
ISBLANK ( 'SCHEDHOUSEDETAIL'[actualfinishdate] )
)
VAR UnsoldCompletedHomes =
CALCULATE (
COUNTROWS ( 'SCHEDHOUSEDETAIL' ),
NOT ISBLANK ( 'SCHEDHOUSEDETAIL'[actualfinishdate] ),
ISBLANK ( 'HOUSE MASTER'[contract_date] ),
NOT ISBLANK ( 'HOUSE MASTER'[Start Date] )
)
RETURN
ActiveWIP + UnsoldCompletedHomes,
'SCHEDHOUSEDETAIL'[activitycode] = "Q75"
)
Alternatively, you could create two separate measures for ActiveWIP and UnsoldCompleteHomes, and sum them in the Total WIP.
Does the above measure give the expected result?
Regards,
Owen
Thank you! Not just for the solution but for the explaination, really helped clarify how the functions work.
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 |
|---|---|
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 3 |
| User | Count |
|---|---|
| 9 | |
| 6 | |
| 6 | |
| 6 | |
| 6 |