# Visibility based on more that one condition

**URL:** <https://community.glideapps.com/t/visibility-based-on-more-that-one-condition/2032>\
**Category:** Feature Requests\
**Created:** [November 15, 2019, 10:23pm UTC](https://community.glideapps.com/t/visibility-based-on-more-that-one-condition/2032 "2019-11-15T22:23:05Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**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 16, 2019, 6:00pm UTC](https://community.glideapps.com/t/visibility-based-on-more-that-one-condition/2032/9 "2019-11-16T18:00:05Z")

</div>

@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 columns that can be used as a condition under Visibility.

All-in-all, I learned something, but didn’t help anybody else.

---

_[View the full topic](https://community.glideapps.com/t/visibility-based-on-more-that-one-condition/2032)._
