Is there a reason I can’t add user input to a string selector if it set to single selection.
Hey tjbeck!
I’ll make a couple assumptions up front, so let me know if I’m off:
- The use case is something along the lines of a user searching through a dropdown to make a selection and they cannot find what they are looking for
- The user wants to add a new selection since they cannot find it in the dropdown
- You are using the string selector widget in workshop
Assuming the above, a user would not be able to add an option and have it saved because workshop has no backend to save that value separate from the Ontology. So if the string selector allowed this functionality, any added values would get wiped out when you refresh the page or just not saved at all.
This functionality is possible in an action form, however, because an added value could get persisted to the ontology.
Do I hear you correctly? What’s the use case you’re imagining? Even as I write this, I could potentially see an instance where there’s a good need to add this feature.
I currently have two ontology objects one is a set of objects with pre defined properties. The other uses that information to pre populate values for object creation. However, I want the user to be able to input a value that is not in the first object. Since it is a temp value I don’t want it saved in the ontology.
With that said I don’t want the user to be able to select more than one object. I am using a string selector. If I set the selector to allow the user to select multiple values they can input a value not listed, yet this functionality does not exist on single selection.
Sorry, to be so cryptic I just don’t know what I am allowed to post, since I am still training. Thank you for your assist.