In the Glide dashoard URL, e.g. https://go.glideapps.com/o/your-team-id-here/
App ID: 49Xp7ZKtmnR5gEDoExl0
In the Glide builder URL, e.g. https://go.glideapps.com/app/your-app-id-here/layout
Description
When I open an Edit screen for a given item (in this case, “Materials”), the visibility conditions seem to be reversed.
The same condition is set to the delete button, and it functions just fine. It appears to be something specific to the “show edit screen” action.
How to replicate
From dashboard… click “Materials”. Then try to edit any of the materials. On the edit screen you will find a hint component that says
“CONDITION: SHOW WHEN DELETABLE IS CHECKED OR TRUE
DELETABLE STATE: (insert state here)”
When state is false, and condition is visible if true, it shows. If i flip the rule, it doesnt show?
Interestingly enough, if i set a condition on the “Show Edit Screen” action, then open the edit screen for a deletable material, the on screen visibility condition works as advertised.
false (unchecked, after that state has gone through true once)
The checked or unchecked boxes in a boolean column do not let you see visually that there are indeed 3 states, since empty and false display the same empty box.
If you edit a boolean column and change it to a text type, you can indeed verify that “empty” and “false” share the same empty box.
this particular boolean is an If then else, with no states leading to null values.
I also have the basic boolean columns in the app default to on, then turned back off via flows when row is written to avoid the null values.
The “Deletable State: False” is pulling the value directly from the if then else column in question, so it is not null.
That also doesnt explain why the exact same column, if used as a condition on the “Show Edit Screen” action, works correctly.
I cant come up with any possible answer besides there is either a bug, or a very weird interaction with the state of computed columns on edit screens. But the output of those computed coloumns (in this case, boolean if then else) appears functional and correct when used in other components on the screen.
ONLY when visibility condition is based on it.
I considered the null value, and tried various combinations of visbility conditions/boolaen true/false/null outputs and its always opposite of what it should be.
I can reproduce the problem @Ja_ke mentioned. It seems like the calculation in that Edit screen for the relevant If-Then-Else column isn’t passed on correctly to visibility conditions.
