[SOLVED] Filter UI: DropDown Value Is Not Applied Until It's Changed

[SimonPain]

I’m submitting a…

• [ x ] Bug report

Minimal reproduction of the problem

• Open the content for a schema
• Click the query button
• Click the “Add Filter” button
• Choose “status” in the first list
• Choose “is equal to” in the second list
• DO NOT CLICK IN THE THIRD LIST
• In my app the third list shows “Archived” is selected
• Click the “Submit Button”

Current behavior

• The error “Validation error. Json query not valid: Expected String for path ‘status’, but got Null…” is shown
• The filter in the URL is: query=%7B"filter":%7B"and":%5B%7B"path":"status","op":"eq","value":null%7D%5D%7D,"sort":%5B%5D%7D

Expected behavior

• The content is filtered to those with the status “Archived”
• The filter in the URL is: query=%7B"filter":%7B"and":%5B%7B"path":"status","op":"eq","value":"Archived"%7D%5D%7D,"sort":%5B%5D%7D

Current Fix

• Clear the query from the URL
• Click the query button
• Click the “Add Filter” button
• Choose “status” in the first list
• Choose “is equal to” in the second list
• Click in the third list and select the option that was already selected
• Click the “Submit Button”

Environment

• [ x ] Self hosted with docker
• [ ] Self hosted with IIS
• [ ] Self hosted with other version
• [ x ] Cloud version

Version: 6.7

Browser:

• [ x ] Chrome (desktop)
• [ x ] Firefox
• [ x ] Edge

[Sebastian]

Thanks, I will have a look. But I will very likely not provide it for 6.X

[Sebastian]

It was a general problem with the dropdown to always show the first value when the current value does not match to any of the available values.