Populate multidropdown value with workflow?

[stomper-steed-0r]

Hi. As the topic indicates, I am having trouble figuring out a way to populate my MD’s value with in my workflow.

If a desired choice is not in the Multidropdown’s list (a DB search return), the user selects the plus, which toggles a group focus containing and input box overlay.

So far so good.

After the user inputs their desired choice and hits enter, the desire workflow is

1. creates a new item in the database for it,

2. [missing step] populate the multidropdown with the newly created DB record (“TEST” below), then

3. toggle the Group focus to hide it again

I have tried various element→send data steps and various workarounds with states, but can’t seem to get it to populate the MD’s value.

Anyone have any ideas?

Any ideas?

CLARIFICATION: As shown in my 3rd screenshot, the newly-create record “TEST” (what was entered in the input box) saves to the DB correctly, and appears in the Multidropdown’s selections list correctly. What I am asking is if anybody knows how to “select” that newly-created record from that list (i.e. add it as a “tag”) in workflows so the user doesn’t have to manually go into the list to select it after adding it. I have added a 4th screenshot of one of the (most likely to work) methods I tried, but for some reason this doesn’t change the multidropdown’s value (i.e. doesn’t “select” it automatically).

SOLVED (finally)!!!

For everyone’s future reference, the workaround for the non-functional (but error-free) “Step 2” shown above, do the following to select it automatically:

1. push the “result of Step 1:converted to list” into a state (type: “category” as list) using “set state”

2. set the multidropdown’s “default value” to that state

Thanks again to everyone who replied.

[Baloshi69]

why [missing step] normaly this happend when a reference is deleted, can you share some screen shot,

when you create a item jusr reset the parent dev of the dorp down and it shuoul take new value but its annoying to user to select that value again. so i suggest when user create a category just add it to user flow.

make it auto select and let user continue

[rjayaddi]

I did the same thing with Multi-Select dropdown, if user didn’t find a suitable category he can add custom one. Here are a few steps you should follow.

1- Pass the date source as Text

2-Check the Box to input value

3-In workflows implement the functionality to create.

If you still have an issue, reply here.

[achen2222]

you are thinking about it the wrong way.

Generally speaking bubble automatically refreshes when data is updated in the database.

So rather than think about your workflow actively pushing data into the dropdown, instead you should think about the dropdown using a search to populate itself with the correct data.

When the workflow updates the database, all user interface elements that use that data can be automatically updated.

So the dropdown source should be a search for …

Then when the workflow adds the database element, the search for of the dropdown will automatically get the new data and the dropdown will contain the new option.

This is the pattern that should be used everywhere as much as possible.

[stomper-steed-0r]

Thanks for trying to help. By “missing step” I mean the step that I want to / can’t create (what you refer to as “make it auto select and let user continue” is exactly the step that I want to / can’t do). Not “missing” as in an error or deleted reference. I added a screenshot of one of the solutions I tried that should, but doesn’t work.

[stomper-steed-0r]

Thanks for trying to help. What I meant is how do I get bubble to automatically “select” it from.the list (i.e. add it as a tag in the MDD, i.e. make it the MDD’s value)? I’ve added clarification and another screenshot above. UX/reducing friction is why I am trying to push it into the MDD’s value (it appears as TEST in the MDD’s selection list no issue).