How to highlight a bar in a graph based on selection in a slicer without losing other values

[Anonymous]

My requirement is to have a Superviser view and a Operator view. The SV would have the KPI graph with all the operator names and values, but the OV should only have the name of the selected operator and all the other values. Basically the superviser would give the OV printed on a paper to the specific operator to show his standing amongst other without disclosing their names.

I have tried different approaches but no success.

[dax]

Hi @Anonymous , 

You could try to use conditional formatting in chart->data color to achieve this goal, and you also need to create table for slicer. You could refer to my sample for details

Measure = if( SELECTEDVALUE(Query1[Attribute.1]) in values('Table 2'[Attribute.1]), "#faba0a","#0a86fa")

Best Regards,
Zoe Zhi

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Does this need to be a table only and not a query with a relationship?

[Greg_Deckler]

Switch your Edit Iteractions from Cross filter to Cross Highlight?

[jithu0]

Hi @Greg_Deckler ,

The edit interactions -> highlight (instead of filter) option is available only between visual to visual interactions. Slicers only filters other visuals. Is there a way to achieve highlight of a visual thru slicer selection rather than on filtering?

[Anonymous]

They dont work on slicers unfortunately 😞

[dax]

Hi @Anonymous , 

You said that this don't work, right? I want to know which part don't work? Did my sample don't work when you open it? You said that you don't want to lose data, so I create a slicer table which don't have relationship between main report, when you click on slicer , it just highlight the corresponding bar.

Best Regards,
Zoe Zhi

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Ok Let me give you a detailed overview of the requirement. Below you see a wireframe. On the right with all the blue bars is the superviser view. Now the superviser wants to approach the operator to show him his standing among his peers. When he does that, he wants to hide all the names of the operator and only highlight the bars which relate to the operator in question.


Now this is how the data model is structured. There are 3 slicers - CREW, LU, SHIFT and all these 3 slicers will filter out the fourth slicer which is the OPERATOR NAME in Shovel Operator. Now this OPERATOR NAME slicer has limited names as filtered by other 3 slicers. So this has to be related and cant be an independent table 

Hope this makes it more clear, please let me know if I can provide any more info.

Thanks,

Anshul