Hi everyone,
I think I may have found a bug with the new Global Expressions feature in the new Bubble editor.
I created a Global Expression that returns a list of Universal-autorizados. The expression has a parameter called organizacion, and this parameter is the same exact data type as the field I am using in the search constraint.
The setup is:
Return type:
Universal-autorizados
List: yes
Parameter:
organizacion
Type: Derivante-Organ...
List: no
Expression:
Search for Universal-autorizados
Constraints:
Superadmin = "no"
org_asistente = organizacion
The field org_asistente is not a list, and it has the same data type as the organizacion parameter.
However, Bubble shows an error when I try to use the parameter in the search constraint, even though both sides of the comparison are the same type. I also confirmed that the “Add” shown next to the parameter is just Bubble’s default UI option and not an operator I added manually.
From what I understand, this should be a valid expression:
org_asistente = organizacion
I’m attaching a video showing the issue.
Has anyone else experienced this with Global Expressions and parameters in the new editor? Is this a known bug, or am I missing something?