Forum Discussion
Slicer Select All Weirdness
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
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......
You're quite right, I edited my reply which means the original was not stated correctly--it was wrong. In truth, I'm not understanding your question's context I guess. If you're thinking that two slicers on the same column is the issue...perhaps you could state that. Perhaps the issue is what are the snips showing. The one on the right is the slicer after hitting select all. The one on the left is clicking individual boxes. The row counts are in the card display next to the two examples.
I have a series of slicers ALL operating on a selection of rows. The rows are then displayed on a matrix and in a slicer for further refinement via a slicer of the provider name. This is a slicer on the same table, NOT the same column as any above. It's not a conflict in that way.
The rest of the conundrum holds true. Click on the select all...and every row in the table is selected--not just the rows highlighted by the slicer. And by the way...it does work the way I'd expect in other situations. Perhaps the slicer's values are too long or some other thing.
Hi - I have exactly the same problem as you've described.
Two slicers cross linked - a) filter on the first then b) choose select all on the second...results in ALL records not just those displayed
I wondered if you ever found a solution?
Thanks
