Forum Discussion

ThomasDay's avatar
ThomasDay
Impactful Individual
10 years ago
Solved

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 t...
General Comment
  • Anonymous's avatar
    Anonymous
    10 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:

     

    1. Create a simple table with duplicate records.(Test4 has 4 records, others has one)

     

    1. Create the slicer and the measure.

     

    Measure: Count of Row = COUNTROWS(Test).

    Result:

    1. 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:

     

    1. Count of Row = COUNTROWS(DISTINCT(Test[Name]))
    2. Count of Row = COUNTROWS(VALUES(Test[Name]))

     

     

    Regards,

    Xiaoxin Sheng

ThomasDay's avatar
ThomasDay
Impactful Individual
10 years ago

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

CahabaData's avatar
CahabaData
Memorable Member
10 years ago

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......