There’s a known limitation when using calculation items in slicers. When a user selects a single calculation item, any unrelated measure on the page — like a title measure or a measure that returns text — ends up showing the result of that calculation item, instead of its intended output.
The usual DAX functions like SELECTEDVALUE or VALUES don't work as expected with calculation groups. Also, excluding unrelated measures by adjusting the calculation items DAX's like using ISSELECTEDMEASURE & IF is not an scalable solution, and it makes the calculation item DAXs much more complex.
One common workaround is to create a separate table with the same metric names and use that for slicers. For this purpose, a relationship is required between this proxy table and the Caclution Group table which is currently unavailable in Power BI. It'd be very useful if this issue was resolved sooner or at least the relationship of the proxy table and the calculation group table would become available.
lbendlin
on:
Fabric Copy Activity Upsert Needs Native Audit Col...
miguel
on:
Personalized Source List in Get Data
on:
RLS testing UI (Test RLS roles directly in the ser...
on:
DO NOT CONVERT my Workspace to Fabric Free Trial W...
on:
MS Fabric: Manage Connections and gateways with Fo...
on:
CU% over time: Filter by workspace (Capacity Metri...
YSD
on:
Support the SSE protocol as Fabric Eventstream sou...