Instead, what it does is to reset the parameter to default before re-running the query and updating the items in the dropdown. I know this is the case, because if I add a “#” to each item in the dataset in another window, and then refresh the filter in this window, the list items are updated, but not filtered.
Can anyone think of a way to achieve the result I am looking for. The point of this is to implement a “needle-in-a-haystack” filter where I keep adding to the filters and reduce the “noise” that I have to look at.
This query is simplified. The actual dataset implements a subquery that counts the number of filter “hits” per entity and checks that it matches the number of items in the filter.
That part works fine.
The issue is how to have the filtered list reflected in the dropdown.
Hi @Jeremy_Likezero,
Apologies from the community for missing your initial posting. A quick note on that, when you add an additional comment/response to a topic, it gets removed from the ‘unanswered’ and ‘new’ sections of the community making it hard to find for others to assist. I would suggest editing your initial post as opposed to adding a second comment to avoid this from happening in the future!
In regards to your question, there’s no great way to limit the values being returned in a parameter without choosing the default value(s) when setting up the parameter. Unfortunately, there’s no built in way to limit the values returned in this manner. I’ve seen a few other similar requests for parameter value limitations so I’ll mark this as a feature request to promote visibility to the support team.
