Some items with a view condition to show itself when a column equals a certain value are doing the opposite (i.e., showing when condition is not met, and not showing when condition is met).
However, there are other items with nearly identical view conditions that do or don’t show as intended.
In my app we have a recruiters table and a vacancies table, where each recruiter can be linked to multiple vacancies (via a column relation). Shown above is a dashboard page connected to the recruiters table, and the filters for this page are shown below (basically it should read data for the recruiter viewing it).
The selected text is showing on screen. However, if we look in the back-end, for this vacancy, this column’s value is set to 1, even though this text is still being displayed. However, the text would hide if this column’s value were 1, giving the opposite of the intended behavior.
The back-end data from the recruiters table (for the viewing recruiter) is shown below:
As you can see the text is being shown when it shouldn’t, and vice versa also happens.
A similar situation takes place with the users table (for the candidates user type), but there the text entries do (not) show as intended by their view conditions. I suspect maybe Glide is not handling the relation data properly? Who knows.
Expected behavior:
The items affected should show when their conditions hold.
Feel free to reach out to me of any questions regarding this, so we can solve this bug together!
In this app we have 2 different user types, namely Recruiters & Candidates. Each have their own dedicated tables to store data uniquely for them, but common user data is stored on the user profile table.
Something seems off to me if it’s behaving the opposite way. When you’re on the edit screen or the details screen of “Data Scientist Inc 1”, can you click the “Data” tag on the bottom left and tell me if the data belongs to that row?
Unless I’m missing something, I can’t see any reason why that wouldn’t be working as you have it.
However, try my suggestion: change it so that it returns true (this will make it a boolean), and then use “is checked/is not checked” in your visibility conditions.
