Using an option set as a parameter for a backend workflow

randomanon · 2024-07-23T11:37:50.815Z

Edit: nvm I found another method of dealing with this issue

adamhholmes · 2024-07-23T12:18:04.911Z

I assume you’re calling the API workflow using the API connector, rather than using a Schedule API Workflow action, correct?

Option Sets are identified by their ‘Display’ property (just like things are identified by their unique ID).

So for Bubble to recognise an option from an option set you MUST use the display property of the option.

Of course, you can also locate the Option yourself using a filter, and ANY attribute of the option so long as it’s unique - you just need to manually filter the options for it…

But if you want Bubble to automatically recognise the Option then you need to use the Display attribute for that - so I’m not sure why you don’t just do that.

Zeroic · 2024-07-23T12:18:42.985Z

Ideally, you can do something like this

{
Option set list :format as text
}

Within :format as text, you can have
“key”: “value”

And the delimiter can be a comma

system · 2024-10-01T11:38:49.399Z

This topic was automatically closed after 70 days. New replies are no longer allowed.