Forum Discussion
Slicer Select All Weirdness
- Anonymous10 years ago
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'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
- ThomasDay8 years agoImpactful Individual
No, I have simply moved on and am unable to use what would be a very useful design. Slicer 1 gets a shorter list, slicer 2 is a refining slicer...where select all selects all of the short list items...and a user can uncheck a few for example. This would be very helpful and simplifying for my needs.
Let me know if you figure something out and sorry for the tardy reply, I was off the grid for 2 weeks...
Tom
- AndyTrezise8 years agoAdvocate IV
I couldn't get the standard slicers to function the way I needed them to so I switched tact.
I now use the hierarchy slicer for my 'child' slicer which works much better and gets around the 'select all' problem
- lushd5 years agoFrequent Visitor
Adding my voice to the list as I am having the same issue, unfortunately a hirarchy slicer won't work for my needs either. Incredible that there has been no improvement in four years, it would be so easy for microsoft to add a toggle switch for "applies to all", "applies to shown" right next to where you enable the select all button.
Has anyone come up with another workaround for this?