# Required choice component behaviour when hidden **URL:** \ **Category:** Ask for Help\ **Created:** [August 7, 2025, 8:35am UTC](https://community.glideapps.com/t/required-choice-component-behaviour-when-hidden/83702 "2025-08-07T08:35:52Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Ramya\_Venkatesh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ramya_venkatesh/32/88271_2.png) [@Ramya\_Venkatesh](https://community.glideapps.com/u/Ramya_Venkatesh)\ **Post date:** [August 7, 2025, 8:35am UTC](https://community.glideapps.com/t/required-choice-component-behaviour-when-hidden/83702/1 "2025-08-07T08:35:52Z")
I have a choice dropdown D1 component. I’m filtering the values in the dropdown based on screen selections in previous dropdowns. So, when there is no match in the D1, the component is hidden altogether. The problem is that this is a required field in the form, and when it’s hidden, the system allows users to submit the form without filling this up. According to Glide’s AI Agent, I can either have a default ‘No items to show‘ option or I can try and mark the field as required only when there is an option available. Both of these don’t help. In the first case, a user can select that option itself and submit the form. Second case won’t work because I want the field to always be filled. In the case where there are no options, I have a button to allow the user to add an entry which can then be selected. Any better solution? Users are able to fill incomplete data right now and the app is behaving in unexpected ways. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [August 7, 2025, 2:15pm UTC](https://community.glideapps.com/t/required-choice-component-behaviour-when-hidden/83702/2 "2025-08-07T14:15:42Z")
The tricky thing here is determining when D1 would not have any choices. As you’re, I assume, in a normal form, the previous dropdowns’ values would be sandboxed inside the form. My suggestion is converting this to a custom form if it isn’t too much to build again. Write the choices to user-specific columns, so you can know on the fly where choices are available or not, and structure your submission availability around that. > [@How do I create a custom form?](https://community.glideapps.com/t/how-do-i-create-a-custom-form/25014): > > I’m just dropping this here so I have something to refer people to when they ask. This is a simple concept app (copyable), that demonstrates the following techniques: Building custom forms for adding and editing list items (as an alternative to the native forms provided by Glide) Preventing duplicate new entries using [User Specific Columns](https://docs.glideapps.com/all/reference/data-editor/user-specific-columns) and [Relations](https://docs.glideapps.com/all/reference/data-editor/computed-columns/relation-column) Enforcing mandatory input items The use of visibility conditions and user specific booleans to control user flow There is nothing particular… There would also be a case where a user enters a choice (when D1 has available options), but then previous dropdown values change, leaving D1 with no options. In such cases, I would have a live list of available options for D1, and check if the chosen value at that moment is included in the list. Only validated if it’s included. ---
**Author:** ![Ramya\_Venkatesh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ramya_venkatesh/32/88271_2.png) [@Ramya\_Venkatesh](https://community.glideapps.com/u/Ramya_Venkatesh)\ **Post date:** [August 9, 2025, 10:24am UTC](https://community.glideapps.com/t/required-choice-component-behaviour-when-hidden/83702/3 "2025-08-09T10:24:57Z")
Aah, changing to custom forms everywhere will be quite some task! I don’t think I can do that atm. Some components have a ‘Show when disabled‘ option. That would’ve been helpful here. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [August 9, 2025, 1:36pm UTC](https://community.glideapps.com/t/required-choice-component-behaviour-when-hidden/83702/4 "2025-08-09T13:36:33Z")
Unfortunately that’s the default behavior. I think your other choice is to write all relevant choices to user profile columns so you have access to them outside of the form. That way, you can also know when the choices are available or not, but you then must control the “Submit” button’s availability dynamically with CSS. ---
**Author:** ![Ramya\_Venkatesh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ramya_venkatesh/32/88271_2.png) [@Ramya\_Venkatesh](https://community.glideapps.com/u/Ramya_Venkatesh)\ **Post date:** [August 12, 2025, 9:33am UTC](https://community.glideapps.com/t/required-choice-component-behaviour-when-hidden/83702/5 "2025-08-12T09:33:13Z")
Thank you @ThinhDinh I’ll evaluate which one is the option for us. Would be great if Glide can fix this though, seems like a ton of work for what could be a simple UI change on the platform.