While it's possible to set (programmatically or via event handlers) a value for a Select component, there doesn't seem to be a way to directly set the inputValue—the text inside the input field that doesn't necessarily correspond to a predefined option.
This would be particularly useful for Select components that allow custom values, as it would enable programmatic control over the input field without selecting a fixed option.
Currently, event handlers don't appear to differentiate between updating value and inputValue, making this functionality unavailable.
@emozio,
As a workaround, would it work for you to set the default value of the select component equal to a global variable, and then in your query, set the value of that variable dynamically?
Thanks for your response. My primary goal was to programmatically set the inputValue, in particular when the Allow custom values has been set to true.
However, it appears this is supported after all. So I guess I had a flaw in my initial testing, I think. It's either that or Retool has already managed to fix this.
In the meantime, I did discover something else that might be worth looking into: while a forced max length is possible in regular text fields (e.g. based on the column length in the database), it's not possible to enforce such behavior when it comes to Select components with the Allow custom value option enabled.
@emozio,
I'm not exactly sure what you are referring to. You mean that in a regular text column in a table, the text is limited in its length based on what the database limits a particular text property to be. But this is not allowed in a Select component?
Where is the Allow custom value to which you are referring?
