problem with table cross-highlighting

[Kangaroo]

Since the May update I have a problem with my table behaviour.

I'm using visuals (bar chart) to show a "filtered" / highlighted list. Users then can select table items to update other visuals in the report. This worked out very well and would do now as well but....

When there is no selection in any visual (top) the complete table (buttom) shows up, which is correct.

When i select a bar in the visual the list will be "filtered" / highlighted which is correct too.

But when i select an item in the table, the list will be completely expanded again with the selected item highlighted. This is actually not what i want to achieve. 

Having a table with like 10-20 items this is not an issue but having a list of like 2000 items (or even much more) this is a problem since i see all items of the list again and it will be hard to select the items i want to use. I need to make the selection in the bar chart visual again.

Furthermore my selected list item jumps up or down "somewhere" when a bigger table gets expanded again like this. It's impossible to see which item was selected.

In my case it does not matter how i set interactions between the visuals, the behaviour stays the same.

Is there any other way to control this behaviour and if not, is it worth to file a feature request about this?

[Anonymous · Accepted solution]

When it comes to interactive visuals, only one of them can affect the filter context at a time. As soon as you click an element of, say, another pie chart or bar graph, that filter context replaces the existing one.

The way around this is to use things that work as "slicers". These work similar to the actual filters over on the right-hand side that you can define(visual-/page-/report-level). There's the built-in slicer, and the chiclet slicer in the custom visuals gallery (there may be others).

You can have as many slicer-based filter contexts as you'd like, but only one filter context from the interactive visuals.

It might be worth a feature request, but it also might be one of those things that architecturally just can't (and potentially shouldn't) be changed.

[Kangaroo]

This explanation makes sence somehow. It's just a pitty that this change has so much effect on productive reports.

I'll try to use slicers instead but will keep a feature request in mind.

Thank you for the quick response!