I am experiencing an issue where the selected value in a Choice component disappears from the UI when I select another Choice. However, the value is still correctly stored in the Glide Data Editor table.
This issue did not occur before. It worked fine until recently, but now it is broken.
This happens across all browsers and devices, even after refreshing, clearing the cache, and testing with a cloned app.
Expected Behavior:
When selecting a Choice value, it should remain visible in the UI and not disappear when another Choice is selected.
Actual Behavior:
The selected value is saved in the table but disappears from the UI when selecting another Choice.
If I check the Data Editor, the previously selected value is still stored correctly, but it does not persist in the layout.
How to replicate
Open the Glide app.
Select a value in the first Choice component (e.g., Q1).
Select another value in the second Choice component (e.g., Q2).
The first Choice selection disappears from the UI, but the value remains in the Glide table.
The same issue happens across multiple devices and browsers.
This issue started recently. It was working fine before, but now it does not work correctly.
The main issue is that the data is correctly saved in the table but does not appear in the layout/UI.
This happens across all browsers and devices, even after refreshing, clearing the cache, and testing with a cloned app.
Nop… still waiting for support feedback. but the problem is only happening in the EDIT page, i copied the same component to the main page, it behaved as expected!
According to support, my setup is incorrect because multiple Choice components are writing values to the same row.
However, I respectfully disagree.
While the Choice components on the same screen do write to the same row, they are each writing to different columns.
If separate Choice components overwrite each other’s values just because they are in the same row,
that would mean a screen can only have one Choice component at a time, which does not seem logical.
Most importantly, this exact setup was working perfectly fine until three days ago.
If this were truly a configuration issue, I would have experienced this problem from the very beginning, but that was not the case.
I would appreciate it if the team could look into this further.
The team is continuing to review your issue. The underlying issue seems to be related to your visibility conditions — if choice components share the same options in each question, the visibility conditions used in the app will come into play and affect the previously chosen options.
As I said, we are continuing to review and will follow up via the Support thread once there is an update.
Please note that values in an EDIT screen are not stored in your data tables until the form is submitted. This is likely what is causing the issue that you are experiencing. To do this the way you’d like, you should consider using a Custom Form.
Just doing a quick test with radio buttons. By design, only one radio button can be selected at a time in a group.
Seems that the radio buttons in this case are all being lumped into the same group. Potentially being given the same group name instead of unique group names for each set of radio buttons (choice component). The name attribute for each radio tag needs to be unique within it’s respective group.
I was able to reproduce pretty easily without using any filters or visibility conditions. Looks like the name attribute in my case is ‘radio-choice-group’ for everything, which is pretty generic.
This issue did not occur before. It worked fine until recently, but now it is broken.
Expected Behavior:
Actual Behavior:
