# Empty, required (filtered) choice component preventing form submission

**URL:** <https://community.glideapps.com/t/empty-required-filtered-choice-component-preventing-form-submission/22205>\
**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:** 1\
**Showing post:** 21

<div class="post-metadata">

**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")

</div>

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)

---

_[View the full topic](https://community.glideapps.com/t/empty-required-filtered-choice-component-preventing-form-submission/22205)._