# Empty, required (filtered) choice component preventing form submission **URL:** \ **Category:** Ask for Help\ **Created:** [February 3, 2021, 7:59pm UTC](https://community.glideapps.com/t/empty-required-filtered-choice-component-preventing-form-submission/22205 "2021-02-03T19:59:08Z")\ **Posts on this page:** 4\ **Page:** 2
**Author:** ![Rasha](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rasha/32/4585_2.png) [@Rasha](https://community.glideapps.com/u/Rasha)\ **Post date:** [February 4, 2021, 7:27pm UTC](https://community.glideapps.com/t/empty-required-filtered-choice-component-preventing-form-submission/22205/21 "2021-02-04T19:27:32Z")
I got past the initial hiccup where I wasn’t able to bind an ITE column to the 3rd choice component. So while we _can_ display some default text where no choice needs to be made, my view is that it’s confusing to ask a user to interact with a choice component only to discover there’s not benefit to that interaction. And unfortunately, there is no way to set a “No Selection” as a default in that field when choices are dynamic. From a UI standpoint, this scenario is often handled by disabling the component: ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/9/a/9a70c2fd7d9eef2c2f441b4b1d153d729fbebbcb.png) I would be sufficient if we could just **DISABLE the requirement.** – For my use case, the bigger problem with a default text ITE approach is that it prevents me from accessing the **unique ID** associated with each combination of choices. Similar to an issue I’m wrestling with in another app, describe [here](https://community.glideapps.com/t/cascading-parent-child-filters-in-forms-how-to-submit-resulting-data/22156). The most critical data I need is what you see in the 4th choice component in the video (I wouldn’t be using that in production). Once I make the send set of choices **Dock-Diesel** , the presence of an artificial “No Choice” somehow breaks that chain. Doing all this outside a form makes no difference. ![docks](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/b/7/b707c95c98d7e421a694a6b9495cf66f32175fef.png) ---
**Author:** ![dinomeg](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dinomeg/32/20650_2.png) [@dinomeg](https://community.glideapps.com/u/dinomeg)\ **Post date:** [February 4, 2021, 7:57pm UTC](https://community.glideapps.com/t/empty-required-filtered-choice-component-preventing-form-submission/22205/22 "2021-02-04T19:57:55Z")
Hmm, yeah this one is getting a little beyond me haha It would be great to be able to apply a conditional “required” though. That could be really useful for things like this and beyond. ---
**Author:** ![Rasha](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rasha/32/4585_2.png) [@Rasha](https://community.glideapps.com/u/Rasha)\ **Post date:** [February 16, 2021, 5:29pm UTC](https://community.glideapps.com/t/empty-required-filtered-choice-component-preventing-form-submission/22205/23 "2021-02-16T17:29:33Z")
Wouldn’t call this a “solve” but best approach I could find was setting conditional logic in custom actions (pre-form) to determine how many choice components get served, which addresses part of the problem. Maintaining multiple forms (6) is not ideal. There’s a trade off to confront if I want the resulting Marina UID **in the sheet** – I can’t submit two values on a choice component (e.g. Marina UID **and** Pump-Out), which means a vlookup in the sheet to get the missing (1-2) values. **Visibility options in forms are crippling.** ---
**Author:** ![NoCodeAndy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodeandy/32/62530_2.png) [@NoCodeAndy](https://community.glideapps.com/u/NoCodeAndy)\ **Post date:** [January 17, 2024, 4:53pm UTC](https://community.glideapps.com/t/empty-required-filtered-choice-component-preventing-form-submission/22205/24 "2024-01-17T16:53:25Z")
[Previous page](https://community.glideapps.com/t/empty-required-filtered-choice-component-preventing-form-submission/22205.md?page=1)