I’m having trouble using a quick select form answer from a previous step in a condition. It seems like only ‘is’ conditions work.
Repro: If I try ‘starts with’ or ‘contains’, I don’t get the same results. I’ve tested this with a Softr DB ‘Select’ type field, and the values are 1, 2, 3, etc.
Hi there,
To help us assist you more effectively, could you provide a bit more information? Specifically:
A step-by-step of your quick select setup and where the condition is applied.
What exactly you expect “starts with” or “contains” to do versus what actually happens.
Any screenshots or a short recording showing the form and the condition in action.
This will help us determine whether it’s a configuration issue, a limitation, or something that needs a fix.
Hi there. You can reproduce it easily. Create a ‘select’ field and use the values mentioned earlier. Then use this field in the onboarding. Screenshots: Form inputs based on Softr DB select field - multiple bugs
Create a new section and add a filter. Currently, only the ‘is’ condition is showing my test section 3. I’m having trouble getting ‘contains’ or ‘starts with’ to work. I was expecting that the outcome would be the same for any of these conditions; showing the section.
I assume that this does not work as you expect it to work because the values of your Select field are only numbers. Can you test this creating another field with mixed values, like “text+numbers” and test “Contains” and “Starts with” conditions again?
This is a simple reproduction. I initially used regular text values, but they didn’t work. Then, I tried adding the numbers as prefixes, but that didn’t solve the issue either.
Thanks for testing and sharing the reproduction steps.
If I’m not mistaken, for Select fields, the most reliable operator to use in onboarding conditions is “is”, since the field stores discrete option values. Operators like “contains” or “starts with” are primarily intended for text fields and may not behave as expected with Select-type values. That’s why the section appears when using “is”, but not with the other operators.
For this setup, I’d recommend continuing with exact match conditions (is) when referencing Select fields in onboarding logic.
Thanks! I’ve been using a different approach, but it still feels like a bug or at least a UI hiccup. Just wanted to let you know. 
Sure, thank you so much for the heads up!
