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