Search in Dropdown Multiselect Filter Doesn't Filter to Selected Values

Q&A
, , , ,
1

I have a multiselect dropdown control in an analysis. The user can type in a value to search, and the dropdown shows the correct relevant values. They are selected automatically, with an additional value for “Select All Results”.

The problem is that the table does not get filtered. It still shows all results and the control says “All”.

Yes, this happens with and without an “Apply” button.

Yes, the filter control is connected to that table.

Yes, the filter works (sometimes) if some, but not all, are manually selected from search results. Sometimes selecting some, but not all results, doesn’t work and it still shows “All.”

Is this user error? A bug? A setting I need to change? This seems like a newer-ish development.

2

Hi @C_B,

I believe this is an issue with how Quick Sight handles “Select All”. When you search and all results are selected (including “Select All Results”), Quick Sight treats it the same as having no filter applied, essentially “Select All” = no filter = show everything. Another user had a similar issue ( Issue with excluding all values in multi select control - #2 by darcoli )

I just replicated this in our environment and got the same result as you did. And as per my understanding this is still something the AWS product team is working on.

I think a workaround is to uncheck “Select All Results” before searching, and then check the specific values you actually want selected. If you search and get 5 results, manually select the 1st one without the “Select All” option checked, then search the rest. That should trigger the filter correctly.

For example:

Here is a table with everything selected":

image
image1701×808 155 KB

1.) Uncheck the ‘Select All’ box:

image
image1708×805 115 KB

2.) Select an option (in this case, a city) before typing in the search bar:

image
image1702×814 150 KB

3.) Now you should be able to search by typing and not get the Select All issue:

image
image1699×811 151 KB

Hope this helps and please feel free to keep us updated with any new developments/questions you have regarding this!

3

Hi @C_B,

Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime.

If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.

Thank you.

4

Thanks for checking in. Yes it seems like it’s not entirely solvable for now. I look forward to this update.

5

I think this is something that has irritated me as well. From a user interaction perspective this is definitely a problem and Quick Sight should change this behavior.

6

Hi @C_B,

I was working on your case and believe I found another workaround. I would recommend creating a parameter for the field you are filtering, selecting Multiple values, and leaving the default values blank. Then, if you link the parameter to the field, it should work as intended.

Hope this helps!

7

Thank you @WLS-Cesar! This is the closest solution.

To operate the filter, you have to

  1. Deselect “select all”. (the default)
  2. Type in text to reduce the filter results.
  3. Click “select all results”.

If you search the filter without deselecting “select all”, the original problem persists. It would still be helpful if this was fixed without having to use a parameter, as I’m certain most people haven’t set up their filters like this, and users certainly can’t do anything about it. But this is good enough for now. Thank you again!