# Force a field to be mandatory if a selection in drop down is selected? **URL:** \ **Category:** Ask for Help\ **Created:** [November 30, 2025, 6:16am UTC](https://community.glideapps.com/t/force-a-field-to-be-mandatory-if-a-selection-in-drop-down-is-selected/85598 "2025-11-30T06:16:48Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![PPF\_Bobbie\_Weeks](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ppf_bobbie_weeks/32/92748_2.png) [@PPF\_Bobbie\_Weeks](https://community.glideapps.com/u/PPF_Bobbie_Weeks)\ **Post date:** [November 30, 2025, 6:16am UTC](https://community.glideapps.com/t/force-a-field-to-be-mandatory-if-a-selection-in-drop-down-is-selected/85598/1 "2025-11-30T06:16:48Z")
Hi all Is it possible to force a field to become mandatory if a certain selection is made in a drop down list? If the selection isn’t made then the field is there but not mandatory? For example, there is a drop down choice of A, B, C and D. The field SELECT is always shown but you don’t have to enter anything into it unless you select either choice C or D. Is this possible and how would I go about it. Thanks 🙂 ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [November 30, 2025, 5:51pm UTC](https://community.glideapps.com/t/force-a-field-to-be-mandatory-if-a-selection-in-drop-down-is-selected/85598/2 "2025-11-30T17:51:22Z")
Just for clarification, you have a choice component and another entry component, and that second entry component is the one you want to be required or not? For something like that I would create two entry components. One marked as required and another that isn’t. Then conditionally show each one depending on the value in your choice component. ---
**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\ **Post date:** [November 30, 2025, 6:58pm UTC](https://community.glideapps.com/t/force-a-field-to-be-mandatory-if-a-selection-in-drop-down-is-selected/85598/3 "2025-11-30T18:58:28Z")
Yep! What Jeff said is best practice. Use visibility conditions to show either a required field or a non-required field based on the screen —\> value. ---
**Author:** ![PPF\_Bobbie\_Weeks](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ppf_bobbie_weeks/32/92748_2.png) [@PPF\_Bobbie\_Weeks](https://community.glideapps.com/u/PPF_Bobbie_Weeks)\ **Post date:** [November 30, 2025, 7:16pm UTC](https://community.glideapps.com/t/force-a-field-to-be-mandatory-if-a-selection-in-drop-down-is-selected/85598/4 "2025-11-30T19:16:08Z")
Hi Jeff This is actually what I ended up working out to do. So for choice A and B I had field 1 display whixh was not mandatory. For choice C and D I had field 2 display and it was mandatory. But what I thien had was field 3 which wasn’t an input field by the user but rather by the submit button. On submit if choice was A or B I copied field 1 into field 2 ans 3. If choice was C or D I copied field 2 I to field 1 and 3. That way if the choice was ever changed, the change was reflected in “real” field 3. Hope that makes sense 😹 Might not be the right way to do it and I’m happy for advice on the right way but it seems to be working. ---
**Author:** ![PPF\_Bobbie\_Weeks](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ppf_bobbie_weeks/32/92748_2.png) [@PPF\_Bobbie\_Weeks](https://community.glideapps.com/u/PPF_Bobbie_Weeks)\ **Post date:** [November 30, 2025, 7:17pm UTC](https://community.glideapps.com/t/force-a-field-to-be-mandatory-if-a-selection-in-drop-down-is-selected/85598/5 "2025-11-30T19:17:49Z")
Oh great. I ended up doing that before Jeff advised but I took it a step further so that if choice was changed, the data in the field (because the fields would change) would update a master field per say. ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [November 30, 2025, 9:05pm UTC](https://community.glideapps.com/t/force-a-field-to-be-mandatory-if-a-selection-in-drop-down-is-selected/85598/6 "2025-11-30T21:05:08Z")
I think I understand what you are saying, but what I would maybe do differently is have both the required and non-required entry components pointing to the same column in the table. That way you wouldn’t need a third field or any On Submit actions to copy things around. ---
**Author:** ![PPF\_Bobbie\_Weeks](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ppf_bobbie_weeks/32/92748_2.png) [@PPF\_Bobbie\_Weeks](https://community.glideapps.com/u/PPF_Bobbie_Weeks)\ **Post date:** [November 30, 2025, 9:16pm UTC](https://community.glideapps.com/t/force-a-field-to-be-mandatory-if-a-selection-in-drop-down-is-selected/85598/7 "2025-11-30T21:16:08Z")
Ohhhh yeah that makes sense! Thanks! ---
**Author:** ![PPF\_Bobbie\_Weeks](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/ppf_bobbie_weeks/32/92748_2.png) [@PPF\_Bobbie\_Weeks](https://community.glideapps.com/u/PPF_Bobbie_Weeks)\ **Post date:** [November 30, 2025, 11:18pm UTC](https://community.glideapps.com/t/force-a-field-to-be-mandatory-if-a-selection-in-drop-down-is-selected/85598/8 "2025-11-30T23:18:32Z")
Oh that works much better! I over complicated because I didn’t realise you could ignore the red warning that says two fields pointing to same column. 😹😹. Thank you! ---
**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\ **Post date:** [January 16, 2026, 5:53am UTC](https://community.glideapps.com/t/force-a-field-to-be-mandatory-if-a-selection-in-drop-down-is-selected/85598/9 "2026-01-16T05:53:08Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.