I’m currently experiencing an issue with the Custom filter list feature in Quick Sight.
Even when selecting “Include” as the filter type, it only matches values exactly, and does not behave as a partial match as expected.
This is causing difficulties in filtering data flexibly, and I would like to confirm the current behavior of the “Include” option in custom filter lists.
If this is a bug, could you please investigate and correct it so that “Include” works as a partial match as intended?
Current behavior of the include option in a custom filter list is that requires exact matches for the values specified in the filter list. The values entered must match the existing field values exactly, partial matching is not supported with Include in custom filter lists.
For partial matching capabilities such as contains, starts with, or ends with, Quick Sight supports those explicitly through the separate Custom filter type (not custom filter list), where operators like CONTAINS can be used for partial matches within a single value filter.
I will mark this as a feature request to promote visibility to the support team.
Since we have not heard back from you, I’ll go ahead and close/archive this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for relevant information.