Aaron on 22 Jun 2016 09:04:52
Currently if you have two unrelated tables with similar columns, a slicer will only show the values of and allow filtering of one of the tables. This means that a user has to provide duplicate slicers, one for each table, where they can select the same values.
- Comments (1)
Comments (1)
RE: Allow slicer to work across multiple tables
This actually sounds more like a data modeling problem. Why do the two tables not share a relationship to a lookup table that contains the values you want to put in a slicer instead of repeating them in each table? I think you could set this up nicely in the Query Editor.