Bubble App Connector - Option Sets

I am struggling to work with data across the Bubble App Connector for option sets and wondering if anyone has any experience or workarounds. I cannot find anything in the documentation for the expected behaviour.

Option sets are public as default and so my assumption was I would be able to drill down and read the attribute values, and the UI of bubble seems to agree by offering up the correct option attributes from the source app to display.

However, the data doesn’t parse with it in the format of (Option with invalid id “” for option set “”) as shown in the screenshot below.

I have tried multiple things, but :

  • Replicating the option set across both apps

  • Using filtering from the new option set to work out the option. However, I can’t find a way to turn "Option with invalid id “” for option set “” into text so that I can extract the ID value.

Has anyone else has any issues with this, or guidance on how to fix?

1 Like

It doesn’t work if you’ve changed the display of the option set. The only reliable way to get it to work is to take a text field rather than option set. e.g Get all options:filtered (This option’s display is text):first item. You’ve provide the display rather than option in the API connector call.

Has anyone ever found a nice way to do this?

The above solution passing display as text or another unique attribute is the most reliable way

1 Like