These are the visibility settings for a hint on my screen, and the same for a button block. The litres filled is definitely not empty and is not the problem, the problem is the 2nd one. It should show when its not checked, yet its visible despite it CLEARLY being checked:
When I change the visibility to when it is checked, it disappears, meaning its reading the value wrong. I added a button on that screen to reload query for that table, still wrong. Refreshed page, still wrong. If I exit the entire web browser and come back in, then it works fine for one transaction but then immediately starts up again for the next.
Any ideas?
I guess my only suggestion would be to check that your screen is attached to the row you think it is.
But based on what you’ve said, I’m inclined to think this could be either a bug or an unsupported use case related to Big Tables.
If nobody else has any ideas, you might be best to submit a support ticket.
2 Likes
Same happened to me today, “Choice Component” visibility is not working properly when pulling data from Glide Table. Need help asap!
Need more details. How is your condition configured? What data is it checking? Is the screen attached to the correct row? Is the data being checked coming from a row under row ownership?
So you are in an edit screen, which is in a semi-detached state from the row. Updates to row data from that screen won’t be committed to the table until you click on submit, so typically I don’t rely on computed columns while inside a form or edit screen. It’s hard to say if your condition is looking at the row before edits or after edits are made, but before the submit button is clicked.
Is your relation trying to point to a row that has a different owner? Don’t always trust what the data editor shows because it has access to all rows, whereas the published app and front end only have access to rows you own.
Jeff, I am very experienced in glide apps and this is not the first time i am dealing with data from glide tables, though this behaviour is not normal and is happening only with the choice component, i was even checking the bugs reports and someone 16h ago has reported something similar. i suggest you run a little test on the visibility of the choice component and let’s see how it goes… i have actually run the visibility to another boolean field from my profile record and it worked fine, but when referring to the current record at hand, it is not picking the information correctly. (btw. the record is already saved, and i am opening the edit fresh with no need to make any modification, only to see the visibility if it works, and it is not… unfortunately!).
Hopefully, someone from support is following this conversation!.. thank you for trying to help anyways 
Update: It appeared that it is not directly related to the choice component as i applied the visibility rule to the container instead of the choice component and the same happened with the container. Also I moved the same the choice component to the main page (outside the EDIT page) and it worked correctly. therefore, the problem in when i am inside the EDIT Page.
1 Like
