PowerBI.tips

Segmented Filtering with Slicers

June 20, 2018 By Mike Carlo
Segmented Filtering with Slicers

This weeks tutorial focuses on the need to control groups of visuals independently.  This recently came up in a project where I needed to adjust all the items on the left side of the screen independently from the right side.  By using the Edit Interactions button found on the Format ribbon you are able to adjust how different visuals interact with each other.  Finally, adding multiple Slicers to the page for controls finishes out the report.  I hope you enjoy this weeks tutorial.

Followup:

On the demo page of the report you’ll notice that when various items are selected, some of the non-selected items dis-appear.  This is handled by using some formatting within the measures for the visuals.  All the measures used in this tutorial are listed below:

Taking an Average of a Numerical Column:

Average of Values = VAR calc = AVERAGE( Data[Value] ) RETURN if( calc = BLANK(), "", calc )

Making Dynamic Titles off of a list of items in a table:

Title = VAR title = CONCATENATEX( VALUES( Data[Customer] ), Data[Customer], ” & ” ) RETURN if( title = BLANK(), "", title )

Producing a sum of values:

Total of Values = VAR calc = SUM( Data[Value] ) RETURN if( calc = BLANK(), "", calc )

Want the file:

Need a little more help? Like the content from PowerBI.Tips.  Please consider purchasing the demo PBIX file to support more great content.

[product id=”17894″ ]

Previous

Data Table Filters

More Posts

Oct 24, 2026

How Deplavity Was Born (and Everything We Made Because of It)

On Explicit Measures episode 573, Mike Carlo tried to say "deployment savvy" and invented Deplavity instead. Here is where the slip happened, how it turned into a fake prescription drug, and every video, ad, and jingle made because of it.

Oct 20, 2026

Fabric Deployment Plan - Ep.573

Fabric deployment plans let you order deployments and run notebooks or pipelines before and after each item lands, which finally gives data a place in the release. Mike Carlo and Tommy Puglia work out which teams should reach for a plan, which should stay in Git and GitHub Actions, and why both would wait for GA.