I’m encountering an issue in QuickSight, and I’m hoping someone can support.
I have a dashboard with a dropdown filter, which should normally show a list of unique values for selection. The attribute I am using for the dropdown filter contains 212 unique values and it turns into a search bar. According to the AWS documentation a dropdown filter should remain as a dropdown when the number of unique values is smaller than 1000.
I’m wondering if Row-Level Security (RLS) could be a factor in this behavior, as I have RLS enabled for this dataset. Could RLS potentially impact the way filters are displayed in QuickSight?
I’d appreciate any insights or guidance on why this might be happening and how to resolve it.
Hello @dkrzl, are you able to still search the values in the dropdown filter or are you not able to find values that you should have access to? I am wondering if there is an issue with the way the RLS dataset is set up. Also, are your using dynamic default values for any of the parameters connected to the controls? That could be causing an issue with the display of the values as well.
I am able to find the values, however the search bar is not an expected behavior and the users are not happy with the look of it. No I am not using the dynamic default values.
I guess it is a feature. I’m not sure where the line is. But at some point you have to scroll to much within the drop-down list that it is better to search anyways.
Hello @dkrzl, I have a thought. I saw you said dropdown filter. Are you pinning a filter to the top of your sheet, or did you build a parameter based control and link that to a dataset field?
Set up your parameter, create a control from it, link that control to the dataset field you want to filter. Then link the filter attached to your visuals to set to that parameter value. That should solve your problem1
Yes exactly! I am pinning the filter to the top of my sheet and at the same time this filter is built based on a parameter with values populated from the dataset field.
I have created my filter exactly as you described. The only thing I didn’t catch is “Then link the filter attached to your visuals to set to that parameter value.” I am not sure if I follow what steps I need to take.
Hello @dkrzl, when you create the control that is based on the parameter and linked to your dataset, it will return the appropriate options but when you select one nothing will change with your visuals.
To link your filters to the control, create the filter for the field that matches the field you set your control to. Then select the custom filter option, filter condition is equals, and click the checkbox for Use Parameter. Then from the dropdown set the parameter that is linked to the control you created.
I’ll post a screenshot below of how the setup looks on my end.
Ok it’s clear now. I have created my filter following those steps in the first place. Unfortunately the filter pinned to the top of the dashboard turns into a search bar. Are there any other reasons when the dropdown filter turns to a search bar (other than when it contains more than 1000 values which is not the case in my example)?
Hello @dkrzl, it is possible that RLS or maybe Dynamic Defaults on your parameters could be causing this if you are not receiving more than 1000 options in the control.
For that specific problem it may be helpful to submit a ticket to AWS Customer support team to help you for your usecase and problem statement. To raise the request, please follow the below link Creating support cases and case management - AWS Support
