Filter widget loses unselected values after selection is made - query logic issue or bug?
I have repeatedly encountered behavior with ExB filters which I think reflects a bug, or at least a profoundly unintuitive implementation:
I have several filters on a single data source in one filter widget. Each filter operates on a different field, and most of them follow the pattern "[Field] is any of [selection]" from the Multiple source type, with "Ask for values" selected and "List values based on" = "All unique values of this field".
When the Experience is opened, the preconfigured filter application and value selections work as intended. When I open the dropdown for one of the filters, the "Show all" and "Show selection" buttons do what they should.
However, if I "Clear selection" for one of the filters, and then select only a couple of options, all of the other options disappear. Whether I have "Show all" or "Show selection" selected, only the selected options are available.
If I then "Clear selection", it deselects the options but the rest of the values do not reappear.
The only ways to get the full list of values back are to either use the "Turn off all filters" button or "Reset all filters" button (which returns them to their default state with multiple selections made for each filter).
I have read similar posts where the issue is the SQL query logic in the filter configuration, but I can't understand why, if all of the records are able to be displayed when the app first loads with multiple filters applied and multiple selections per filter, they would disappear when the user starts to manually change filter selections. In any case, it seems like "All unique values of this field" should ensure that all unique values of the field are indeed displayed regardless of other filter settings, otherwise I would have selected "Values filtered by previous expressions" or "Values filtered by all other expressions". The behavior seems like the filter selection is immediately applied to the data source, thereby limiting the data the filter is available to see...
I have not tried manually defining all of the options and using the Multiple (predefined) source type, but this shouldn't be necessary (especially if I have a field with 100 different values).
Any insights, explanations, configuration suggestions, or confirmation that this is strange behavior would be very much appreciated.
