Forum Discussion
Slicer Select All Weirdness
Hello Fellow Dax'ers,
I'm very surprised at the behavior of "Select All" within a slicer. Here's an example:
Build a slicer with Single Select off, Select All on.
Cross filter this slicer so that a few rows are shown in the slicer. Check a few boxes--all's well. The records checked are selected.
Now check "Select all"---and at this point the boxes shown in the slicers are checked, so far so good...but actually EVERY record is checked. The cross-filter doesn't restrict the Select all in any way. Weird.
That sure doesn't seem right. Tom
Hi MbProg,
According to your description, the Select All feature is enabled for the slicer. When you check multiple individual values in the slicer, the card will display the correct row count values. But if you select all values by checking Select All option, the card displays wrong values, right?
Below is my test sample:
- Create a simple table with duplicate records.(Test4 has 4 records, others has one)
- Create the slicer and the measure.
Measure: Count of Row = COUNTROWS(Test).
Result:
- Choose the ‘select all’.
In summary, the slicer shows the distinct value of column(eg: Name) you placed in the slicer. Maybe some duplicate records are in your table(eg: Test 4), though you choose the 'select all', it will count rows for all records which are related to checked slicer values.
In addition, if you want to get the distinct value of the row, you can try to use below formula:
- Count of Row = COUNTROWS(DISTINCT(Test[Name]))
- Count of Row = COUNTROWS(VALUES(Test[Name]))
Regards,
Xiaoxin Sheng
12 Replies
Hello,
Still, 1 year and a half the last message, the same issue not corrected. 2 slicers, 1 filtering the 2nd, and the "select all" on the second shows the full table content the slicer is related to.
Don't understand how it has never been fixed...
Kr,
Elorian.
you have 2 slicers on the same page referring to the same table/field? ..... that confuses me.....
Edit: Yes, that is exactly true. These slicers are cross filtered...and as such they operate to slice the file further with each one. (It depends on the structure of the file naturally, but these all operate on different columns. Pick a bed size, state and so forth to narrow things down, then pick from the filtered slicer of names.)
That's very common and customary for a file with a series of demographic/attribute columns. So the filtered list of names--can be left alone--in which the full set remains the selection...or picked singly from the list to further refine. The use of the "Select All" in this instance is used to allow someone to pick the full slicer list and then deselect a name or two to refine.
So--that's more context of this example. And the "select all" picks every possible record in the table rather than the list shown.
Tom
sorry we're not in sync: I asked originally if you had 2 slicers on the same page operating on the same column
you replied with: that's exactly true .... but then stated.... they work on different columns
soooooo.....
I definitely have had 2 slicers on the same page working on different columns without a problem and so still wonder about whether they are both actually attempting to work on the same column..... sorry to prolong this......
Hi MbProg,
According to your description, the Select All feature is enabled for the slicer. When you check multiple individual values in the slicer, the card will display the correct row count values. But if you select all values by checking Select All option, the card displays wrong values, right?
Below is my test sample:
- Create a simple table with duplicate records.(Test4 has 4 records, others has one)
- Create the slicer and the measure.
Measure: Count of Row = COUNTROWS(Test).
Result:
- Choose the ‘select all’.
In summary, the slicer shows the distinct value of column(eg: Name) you placed in the slicer. Maybe some duplicate records are in your table(eg: Test 4), though you choose the 'select all', it will count rows for all records which are related to checked slicer values.
In addition, if you want to get the distinct value of the row, you can try to use below formula:
- Count of Row = COUNTROWS(DISTINCT(Test[Name]))
- Count of Row = COUNTROWS(VALUES(Test[Name]))
Regards,
Xiaoxin Sheng
Hi -
I'm having the same issue. Is there a solution?
I have two slicers, one that selects and filters to a recipe and one that allows selection of the ingredients within that recipe. Most of the time the user will want to use "select all" to filter for all of the ingredients in that recipe, however, when "select all" is selected, the table defaults to all of the ingredients in the entire database, not specific to the ones listed for that already selected recipe. The only option I have found is to individually select each ingredient in the list with the control key, but that is very tedious when there are 10+ ingredients in each recipe.
The data in my tables is specific to the ingredients as a whole, not specific to the recipe, so I can't use a hierarchy slicer because my tables are set to not interact with the recipe filter, just the ingredient filter (so combining the two fields into one slicer means my tables no longer show the data as intended).
Hoping someone has figured out a solution to this one!
I am having this same issue with a new data set. I have a list of ~600 records to filter a list of ~7000 records and when I select any number of the 600 up to 599, it filters the report perfectly, but if I select all, it filters none. I haven't experienced this behavior before, so it is quite bewildering to me.
