I’ve got a single select field that is field hidden from a modal where the user makes some other inputs. Certain single select values have been causing a glitch wherein the value is filled at first and then clears out. There are a handful of buttons affected in the same way on the same page. I’ve checked the settings many times and everything is correct. What else do I need to look for, what am I missing? I’ve synced my data and scheme many many times because the affected single select values are newer (were added 3-4 weeks ago). Everything looks correct, I’m lost.
This is the most recent field that I experienced, it’s set correct. Permissions are correct and it has happened with me and other users.
This problem persists and is a daily disruption for us now. Here’s a video showing the issue. There doesn’t seem to be any pattern to when it will happen, its consistently inconsistent.
You can see in the background that the change initially takes place and is reflected in the dertails header (substatus reads “Ready to Start”) but then doesn’t stick. It also isn’t reflected in the airtable record at all. There is also a similar single select for “Status” that is hidden filled in this scenario in the same way with no issue.
@onlymatt thanks for writing this up and sharing the video.
Is it only when it’s used as a default value?
If you removed the default value and made the user choose the value, does it work?
Could you DM us the URL of that page so we can confirm?
I’m almost certain I’ve solved the problem. The buttons in question were all copied from another button where the single select options were limited for user input on the form. After the button was copied and altered for a hidden single select value, that corresponding value was unchecked on the input side. Theoretically if we’re setting a hidden value it should disregard everything on the other tab but that doesn’t seem to be a reality. I’ve also seen where having the required field checked with conditions can cause issues if the field is hidden so that the user can’t submit the form.
That might actually explain it @onlymatt - so you were able to fix it here?
And it’s because the field was set to ‘Hidden’ but there was other config that was still being applied?
Correct. I’ve now tested on 3 different buttons and selecting the relevant value on the “input field” tab did solve the issue even though its a hidden value.
Thanks for spotting this @onlymatt - we’ll add that to our list of things to look at
Hi @onlymatt - I know we fixed your issue here, but I wanted to follow-up to say we’ve fixed the original issue.
If you’re using a hidden field, but previously had some configuration setup on the field, that config is ignored when hidden
1 Like
thanks, thats great to hear
