AH
Ashley Hernandez · Mar 26
you can connect the dropdown to a TinyTable. basically if you have your product list in a table (or import it there), the dropdown pulls options straight from a column. so when something gets added or removed from the table the form just picks it up automatically
we do this for a vendor selection form at work - about 80 vendors in a table with a status column, dropdown only shows ones marked active. vendor leaves, we flip the status, gone from the form. no one has to touch the form itself
for your department thing its even easier, just a single column table with the names and point the dropdown at it
theres actually two ways to handle this depending on your situation
first one is what ashley said, connect it to a TinyTable. works great when you maintain the data yourself and want it to just stay in sync
second option is if your data lives somewhere else like a CRM or some other system. in that case you can go to the Settings tab on the dropdown question type and define a variable there. then whatever page is loading the form can pass the values in when it renders. so if you embed the form on your sales portal the portal can push the current product list into the dropdown without you duplicating anything
the variable thing is nice when
- values come from an outside API and you dont want to copy them into a table
- you need different options depending on who is filling out the form
- the parent app already has the list anyway
for most people id say start with TinyTable since theres zero code involved but the variable route is there if you need more control