Services Plugins FAQs

In my dev database I noticed 7 issues and they all are related to selectize dropdown

Help Needed
#1

my workdlows for all items look the same:

image
image724×445 16.6 KB

I know there is now a mismatch. The field wants a record id (unique ID)-Decedent. But why is it saying text after years of using Selectize?

#2

Hi @markp,

Welcome to the Bubble community, and thanks for sharing the details - this is a good catch, and the confusion here is totally understandable.

What you’re seeing is not that Selectize suddenly “became text”, but rather that Bubble has become much stricter about type validation, especially in backend workflows.

Here’s what’s happening under the hood:

Selectize (Multi) Dropdown has always returned text values - typically the option’s value or label. In many older apps, this “just worked” because Bubble used to be more permissive and allowed text to be saved into fields that logically represented a Thing (like a Decedent), without enforcing the actual data type.

Recently, Bubble introduced stronger backend workflow checks, and now it explicitly verifies that:

  • A field of type Decedent must receive a Decedent thing (unique ID)
  • Supplying text (even if it visually represents a Decedent) is flagged as an issue

That’s why you’re now seeing messages like “value should be Decedent, but right now it is text”, even though this setup worked for years.

Important clarification about Selectize:

  • The plugin does not return Things
  • It returns text (or list of texts)
  • This behavior has not changed in the plugin

Recommended ways to fix this

You have two clean options going forward:

  1. Use Selectize to store the Decedent’s unique ID as text, then
    → Run a search in the workflow to find the Decedent where unique id = Selectize's value,
    → Save the resulting Thing into your Decedent field.
  2. If you only need to store/display a name (not a relationship),
    → Change the database field type to text instead of Decedent.

Bubble now expects this extra step explicitly, especially in backend workflows, and that’s why all 7 issues are showing up at once - they’re all hitting the same stricter validation rule.

You can find more details about the plugin’s returned values here:

If you’d like, feel free to share a bit more about how you’re populating Selectize (labels vs values), and we can confirm which approach fits your case best.

Best regards,
Support Team
Browse all Zeroqode Plugins for bubble
Banner_Last3