Short list vs Metadata - efficiency/Google penalty cost?

Fellow Bubblers:

I’m brand new in using any no code software.

Help!
What is the best practice to handle data types with a short list? In Data or Workflow or both?
Create the short list of values (How?) or create a metadata table with the list of values in Bubble Data (How to access this list of values from another table)?

Thanks~

What do you mean by ‘short list,’ what is it you wish to store?

Thank you for responding, nfisher!

I have an Account “table” in Data with Account Type (with a short list of values like “Volunteer”, “Admin”, “Other”). Depending on the Type, I want to bring up a different page.

I’d recommend creating an option set for these. So an option set called “Account Type” with those values.

On the User data type, you’d have an “accountType” data field where the type is “Account Type” (linking back to the option set).

Learn no code → nocodify.com

1 Like

You should use option sets for this kind of user type categorisation.

1 Like

Thank you, Nocodify!!!

Thank you, nfisher!

Nocodify:

Do I create a new attribute for each value like “Admin”, “Volunteer”, etc.?

No, just options.

Yep, essentially options that are like list of things that are loaded with any page they’re included on

So if you have an option set for roles, create a new option for each role in that set

For attributes, that is so you can associate different pieces of information with each option

As an analogy, think of attributes as a different field for data types.

1 Like

This tutorial should help: Navigation for User Roles

2 Likes

Thank you, jared.gibb!

Thank you again, Nocodify!