I am building a garden app, where I store some information on what plants are native to a region. For some reason I don’t get the option to store the user input in the database field, and I am not sure why.
App setup
I have one table with “plant facts”, and then a table “Regions” with “areas”. The user has the right to use autobinding on all the fields both in the plant facts and regions table.
In the table with “plant facts” I have a field “natitveTo” which is a ‘List of Regions’ Datatype.
Problem
On the page itself I have a dropdown input, that uses dynamic values to search - and that is all good. The only thing that is not working is selecting the Regions as the data to save, because the datatype is not appearing in the selection dropdown. Instead the app is only offering me the option to create a new field.
On the first image is the non working dropdown. On the second another input on the same page, with a similar mechanic. The only difference between the two is that the Source Input field is a list of a different type of thing.
This situation is that you likely do not have a data field on the Regions data type that can be modified, either because the fields are all lists or there is not a type of thing set for the parent element of the dropdown.
This is not an input element despite it’s name. The name may read Input because you may have on an input element used the replace feature to replace it with a drop down element and did not rename it.
In this situation the dropdown element named input has a parent element with a thing set, which is likely the page that you have set the content type to PlantFacts
Thank you for your reply.
I do have data in the Regions table, which I am referencing. Oddly enough it let’s me configure this field when I create a new field for this and set it up in exactly the same way. So it feels more like a bug.
Yes, both examples are dropdowns, hence as I said, they are the same apart from the data field they are referencing.
yes, which is why it is likely that the dropdown that has regions is not contained by an element that has the type of data set to one which has a data field of Regions
Show the setup of the dropdown for Regions to verify if it is in a container with a data type set to a data type that has a field for Regions and the database structure to verify if you have a field that can be modified as Region for that data type you are trying to modify.
I’ve figured it out.
The data field I needed to recreate in the UI, otherwise this was just not showing up, but then it worked. (I am very sure this is a bug, since I set up the new data field in exactly the same way as the old one.)
I needed to use the multi dropdown Input, which needs to be installed additionally, and then I can also save the data.
For other people coming back to this in the future:
This is how I set up the Multi Dropdown:
install the free Multi Dorpdown plugin from bubble in your app (not the 3rd party ones). Then you can select this as an input from the sidebar. I needed to refresh the
I used the current pages items values as Default value, because then you can edit the list as is.
When storing this input in the workflow, I chose to change the field “nativeTo” to “set list” and the the dropdown input as value. This way the whole list is replaced with the current input.
In my case I wanted to store a list of regions. The regions field in my DB is set up as a list of Things (in my app the regions)
The autobinding was not necessary for bubble to store the correct values.
