Hi @duesouth ,
Power BI doesn't allow you to use a measure as a slicer or directly in visual-level filters because measures are context-dependent and recalculated on the fly. To filter the average grade card by how often a pupil has been sent to the Hub, you need a calculated column that counts the number of times each pupil has been to the Hub. This column can then be used in slicers or as a filter on visuals.
You can add the following calculated column to your Pupil_Data table or whichever table you're using as your base for visuals:
NumberInHub_Column =
CALCULATE (
COUNTROWS ( Behaviour ),
FILTER (
Behaviour,
Behaviour[Behaviour Type] IN {
"B7 The Learning Hub",
"B7 The Learning Hub - 3 Strikes",
"B7 The Learning Hub - Lates",
"B7 The Learning Hub - No PROUD Card"
}
),
Behaviour[External ID] = Pupil_Data[External ID]
)
Once this column is created, you can use it as a visual-level filter in your average grade card. For instance, set the filter to only include pupils with NumberInHub_Column >= 5 to evaluate the impact on students with frequent Hub events. Your average grade measure like this:
Average Grade = AVERAGE(Assessment[Grade])
will now respond to the filter and only show the average for students who meet the specified Hub visit threshold. If you want slicer interactivity, you can also create a GENERATESERIES table and use the selected value from that slicer to filter visuals based on this calculated column. This avoids the issues you faced with measures not being accepted in slicers or filters and gives you the control you need.
Best regards,
