Different Option Sets for LIVE vs DEV

[openhousevisitors]

Is there a way to set attributes in option sets that later lets you select which items to display in production vs live environment?

For example I have schedulers running according to selections in dropdowns and I only want certain items shown in the Live environment.

[mikeloc]

Hi there, @openhousevisitors… if I understand your post correctly, give this a shot. Add an attribute similar to the following to your option set, and set each option’s attribute appropriately.

Then, use a conditional like the following to filter the option set to show only the live options when the app version is the live version.

Finally, have a drink to overcome the mind-bending logic of the Isn’t live version thing because there’s a reason for why it’s worded the way it is, but I can’t remember for the life of me what that reason is.

Hope this helps.

Best…
Mike

[openhousevisitors]

Thank you so much. Worked like a charm. …and thank you for providing the sample screenshots as well.

As far as the mind-bending logic of Isn’t live goes, I have to assume that the architecture of Bubble itself requires a default value which likely is set to “YES”. This in turn forces them to backwards engineer the field display so that it always defaults to the Development version unless it is changed by deploying the current version to LIVE… I mean why else would you do such a backward thing?
Thanks for your help.