Anyone noticed that when using custom states for filtering searches the “ignore empty constraints” option doesn’t work?
I am saving search parameters in states for users browsing for produts. The sates are lists that contains brands, price range, etc. Each state is a list of a specific info.
Then I have a RG of products filtered by the states, but I am getting no results unless I populate all the states, which leds me to the conclusion that empty states are blocking the results.
Anyone else feels this should be different?
Edit: Same thing happens if I use a multidropdown as the filter. When it is empty, no results, even with the ignore empty constraints option checked. So it seems the problem is with lists, nos states…
Hey folks! If you’re noticing that something isn’t working as expected, please do file a bug report if you have not already done so. This will allow our team to investigate and take the appropriate steps.
I got an issue to the bug report I had filled but I seems that the team was not able to understand the issue using my actual app page.
The issue exists. I am not sure it can be fixed, but I know we can definetely work better on this.
The page I sent in the bug report has many filters and is not the best example to show what’s happening.
So I created a new test page in a sample app to show the “ignore empty constraints” issue when using lists.
In this app, I created a data type “products” and an option set “brands”. Each product has a field “brand”.
On the page, there are three RGs. The first one is a list of all “brands”. The second is a list of all products and the third is a list of products filtered by a custom state which is a list of brands.
If you click on any of the brands in the first RG, it sets a state to the page and includes the current´s cell brand. The state is the list of brands, wich is used to filtered the 3rd RG.
You will see that initially, on page load, the 3rd RG will be empty, even though the option to “ignore empty constrains” is check in the 3rd RG. Only when you populate the custom state it starts to show the results. If you clear the state, the results will be null again.
Please take a look at this new sample page and see if this can be achieved when using lists as filters. If not, I’ll have to redesign my search criteria.
Conditions with custom states are not working properly