Ok, here’s how I’ve been doing it: https://bubble.io/page?type=page&name=autocomplete_create&id=forum_app2&tab=tabs-1
Thanks
I have to say … that’s just slightly weird UX. Even knowing what it was supposed to do … it wasn’t natural.
What would Material Design say @lonetour ?
p.s. nearly a year since I asked for this 
Well I would do this indeed. Changed a few things, but overall that’s how I’d do it.
It doesn’t feel very reliable. Once you have “added a new item” you need to type it again to make it the “Selected Value”
And quite by accident, I managed to create lots of “Grapefruit” but with different numbers (in brackets) which then disappear on the RG but remain on the drop down.
That first issue is a bit tricky. if you guys think I should remove this happy to, let me know. Adding more stuff isn’t a quick win.
1 Like
Hell, it’s all way better than I could ever do… let me sleep on it and try again in the morning.
thanks a lot for this. Will have a look in detail and feedback.
Scrappy, but this is as far as I got.
3 Likes
Quite nice!
I’m trying to think of use cases for this.
So, for example, if I have a website about travel blogs. and I want to add a city…
If I have a dog website and I want to add a new breed…
Maybe if it said “Choose” not “Search” it would feel better.
I still can’t help thinking that it’s not quite right somehow. It’s hard to figure out why.
For my money, I’d still love to have a dropdown that users can add to… as they have created the list in the first place, they’ll know what’s on it, and will want to click the dropdown. Sure, if it’s a long way down the list, they might be better typing a couple of letters (just one doesn’t work!).
Of course, I can’t find a real life example… so maybe I am too cutting edge for the internet!!
(Also, I’d put ACCEPT on the right and CANCEL on the left of the dialogue box… https://material-design.storage.googleapis.com/publish/material_v_8/material_ext_publish/0Bzhp5Z4wHba3a2tRMk1qRXdOclE/components_dialogs_content1.png)
I like it. @emmanuel I think it should stay
1 Like
Also found that it doesn’t discriminate with Capital letters.
banana and Banana
I’m sure if we play around with some conditions we will find a way
1 Like
I’m certainly not for getting rid of anything… The more the merrier… More toys, more people working on the problem…
I still would like the same idea but with a drop down, if that’s technically possible…
If we could style the search box input field and menu as we do in a RG or group (draging content into it), it would be veery cool.
Can we use a search box inside a RG to do this?
4 Likes
I would love that too.
Also to display the dynamic list by default.
1 Like
I’m having the same issue, I want to allow people to add a wine to their wine cellar and specify the appellation, and if the appellation isn’t already in the database to allow them to create it themselves. For example, if they’re adding a wine from Santa Barbara, the data entry will either have the typed text “Santa Barbara” or the value of “Santa Barbara” if it is already in the database and the select it when filling out the search box.
Because the search box input will always either be an input’s typed text or value (not both from what I can tell), I’ve made a work-around where I just create a hidden input and have the initial content be both the visible input’s typed text AND value, but this seems a little sloppy.
I think an alternative approach would be to input both options into the database at the same time… “data = input appellation’s value AND input appellation’s typed text”, somehow concatenating the two since inherently one will be blank. Is there a way to concatenate these when creating the data entry, instead of using an intermediary step as I have?
Can you make the typed text auto-binding as well? That’s the only thing I’m missing.