# Enable fields based on other fields **URL:** \ **Category:** Ask for Help\ **Created:** [October 31, 2019, 12:02am UTC](https://community.glideapps.com/t/enable-fields-based-on-other-fields/1549 "2019-10-31T00:02:43Z")\ **Posts on this page:** 1\ **Showing post:** 13
**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 21, 2019, 5:55am UTC](https://community.glideapps.com/t/enable-fields-based-on-other-fields/1549/13 "2019-11-21T05:55:07Z")
This presents new difficulties. I’m going to go ahead and say it’s not possible to do the yes/no lookups in add/edit mode. Potentially it might be possible in detail view when using entry fields, but the record would already need to be added at that point. I had already attempted something like this with no luck and included a thread link below. Maybe if you could somehow encode 4 unique character combinations into your location name. So your location Choice Component would look like “Location 1 E-W-”. You could set you Visibility condition to use the Contains operator. If the location contains “E-” then show the Employees component and so on. That’s kind of the best idea I have for now. > [@Visibility based on more that one condition](https://community.glideapps.com/t/visibility-based-on-more-that-one-condition/2032/9): > > @Mark Looking at @Gerard_Fernandez question again, I may have misunderstood his question. I didn’t realize he was in an Add/Edit situation, so I don’t think I have a solution for him. As for a Visibility condition based on Relation/Lookup I think I may have set it up wrong. I was using a Multiple relation with a Lookup column against that Relation. I changed the Relation to be a non-Multiple single relation. The Lookup column I created against that relation now shows up under the list of co… --- _[View the full topic](https://community.glideapps.com/t/enable-fields-based-on-other-fields/1549)._