# Setting a visibility condition for a component on that is dependent on a Relationship Value **URL:** \ **Category:** Ask for Help\ **Created:** [July 9, 2020, 7:40pm UTC](https://community.glideapps.com/t/setting-a-visibility-condition-for-a-component-on-that-is-dependent-on-a-relationship-value/12230 "2020-07-09T19:40:00Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![Fassil\_Befekadu](https://avatars.discourse-cdn.com/v4/letter/f/df705f/32.png) [@Fassil\_Befekadu](https://community.glideapps.com/u/Fassil_Befekadu)\ **Post date:** [July 9, 2020, 11:47pm UTC](https://community.glideapps.com/t/setting-a-visibility-condition-for-a-component-on-that-is-dependent-on-a-relationship-value/12230/5 "2020-07-09T23:47:25Z")
The logic was based on a billing app I created that utilized the method outlined in the below link to make sure that previously selected choices have been eliminated: > [@Eliminate choices after they've been selected: Many-to-many relations](https://community.glideapps.com/t/eliminate-choices-after-theyve-been-selected-many-to-many-relations/9726): > X is not static. It represents the Relationship outlined in the above link that keeps track of the selected choices. Every time a choice is selected, Relationship value is incremented by 1, and the number of choices reduced. I hope that makes it cleared. Thanks for your help on this, @ThinhDinh. --- _[View the full topic](https://community.glideapps.com/t/setting-a-visibility-condition-for-a-component-on-that-is-dependent-on-a-relationship-value/12230)._