Option Set operators not behaving as supposed to

chesk514 · 2025-01-22T17:32:12.009Z

As you can see i put a constraint in RG (which shows a list of PO’s) that “accounting” role can see PO’s only from “Approve” and above “status”, but now i see “Pending”-status-PO’s still showing up to “accounting”, what could it be?

(in my option-set list “pending” is below “Approve” in the list)

davidb · 2025-01-22T18:58:04.038Z

AFAIK, configuration sequence within an option set governs only the sequence in which options display for your selection in the expression editor–i.e., not their sort sequence within the app, which is alphabetical based on each option’s display value. Instead, add an number attribute to each option that you can reference when you need to consider the hierarchy of option set values.

akamarski · 2025-01-22T19:00:50.111Z

Or set is not the values you don’t want
Or set is the values you want

chesk514 · 2025-01-22T19:29:01.303Z

(Bubble actually gave me those operators after the Status name, which makes me think that this IS made for that)
And using YOUR technique how would i write it as a constraint? “Status” = ???

davidb · 2025-01-22T19:46:04.206Z

chesk514:

(Bubble actually gave me those operators after the Status name, which makes me think that this IS made for that)

Sure–comparison operators apply to alpha values, but they’re compared alphabetically (oer perhaps based on unicode value), and not based on configuration sequence within an option set.

chesk514:

And using YOUR technique how would i write it as a constraint? “Status” = ???

Status is in All Status:filtered[This Status's Hierarchy ≥ Approved's Hierarchy]

system · 2025-04-02T17:32:23.123Z

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