I have two searchfields for my table. One to search by name, and one to search by number.
The search by number field is of type number, however the database column with numbers is set as 'string', because sometimes the input data is other then a number for example A01, or 23C3.
I set the SQL mode to; 'run automatically' for both queries.
The query of the name searchfield runs automatically whenever there is any input, however the query of the numbers search field, does not. I have the click somewhere or press enter before it runs.
Hi @ellenhelena Thanks for reaching out! Are you using the on "Change" event? If so, it is expected to trigger whenever you click the up down stepper buttons, when you click away from the component after making a change, or when you click enter
We have an internal request to enable on change events to trigger any time a new value is typed into the component (without the need for clicking away or enter) - which would match the text input. I'll reach back out here when it ships!
Thank for the reply. I am not using the stepper buttons, as the end user at times has to go to 210 for example. I made them invisible. I just used a normal query to run it, see attached.
The number inputfield which I use as a searchfield. Together with a confirm button, it is the most important feature of the application. Hope this will be fixed soon
Also I was wondering, is there an overview somewhere, where I can see which features Retool is working on behind the scenes?
I really like working with Retool, however I've had several times where I got stuck and though it was due to my code, so I spend hours on it to fix it, just to discover that it wasn't my code but instead something that Retool was working on
It would be great if there is an overview, so when I get stuck I can check if it is something that is already in the pipeline, so I won't lose time...
Hi @ellenhelena Thanks for the feedback! I'm sorry to hear it's happened several times
If you ever need a gut check, you're always welcome to post a question on the forums or join office hours
We may expose our roadmap or current bugs in the future, but it's not something we're currently planning to do. I know we've gotten similar feedback from other users, so it's definitely something I'm asking about internally
Any update on this? I really need the number input field to run automatically when changing the input. At the moment I still need to press enter or click somewhere random...
Not currently Wish I had better news for you! It's still in our queue to be picked up
In the meantime, it might be worth exploring whether you could create this functionality in your own custom React component
Could you please check for me how long it approximately will take before this is fixed?
This is the most used functionality of our application - to search bynumber with the numbers input field. As the end users aren't used to click 'enter' after typing in the right number, the users can make mistakes by updating the wrong row. For example the last one selected or no row at all instead of the one typed into the numbers search field..
I have been waiting for two months for the update of this field. So if it's not going to be fixed, i'll have to re-design the application. Which is okee, but from UX perspective not preferred..
Would be great if you can check for me íf or when it will be fixed. Thanks
Unfortunately, since it hasn't been picked up by our team yet, I don't have a timeline. Things can certainly change, but as of now, this has not been prioritized as a ticket that will be solved in the near term I'd recommend exploring a custom component (or refactoring the app if you prefer)
Something like this could be pretty quick to implement (you could add css to make it look like the Retool components)
I think you could potentially solve your case with the
.inputValue property - instead of the
.value - to track user inputs. I tested it a bit & it looks like this should work well the one caveat I see is that if you have a clear input button on your number input component & the user clicks it, the inputValue is 0 instead of null