# How to design Choice component so as not to include an option that has already been selected in the past **URL:** \ **Category:** Ask for Help\ **Created:** [June 22, 2020, 10:30pm UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289 "2020-06-22T22:30:43Z")\ **Posts on this page:** 13\ **Page:** 1
**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:** [June 22, 2020, 10:30pm UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289/1 "2020-06-22T22:30:43Z")
I have a billing app designed to enable Billers to send bills to Payers. Each Biller has multiple bill titles with each bill title having its own Payers. A Payer can be listed on more than one bill. I would like to enable Billers to add (or remove) Payers to any Bill using the Choice component. As part of this functionality, I would like Billers to have the option of adding a brand new Payer OR a Payer from another bill title. What is the best way to design in such a way that when a Biller wants to add a Payer to a Bill, that: 1. I automatically not include a Payer among the choices if he/she is already on the bill they are being added to? 2. I allow Billers to select Payers from any other bill title OR select a brand new Payer? I would welcome any input or guidance both in the google sheet design and glide data design. Thank for any help on this. ---
**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:** [June 23, 2020, 1:25am UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289/2 "2020-06-23T01:25:57Z")
Take a look at this to see if it helps: > [@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): > ---
**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:** [June 24, 2020, 9:42pm UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289/3 "2020-06-24T21:42:48Z")
Hi @Robert_Petitto. This is very useful - thank you. Your Part 2 explanations are applicable to my add. I have an Administrator (Biller) who assigns Teams (Payments) to individual persons (Payers). However, I am having trouble creating the Form Title in the User Profiles (2:38 of your video where I am supposed to create the equivalent of “Team Assignment For Robert”). I can extract the value for the PersonName from the Relationship I created using a Lookup. However, when I try to use a Template in order to create "“Team Assignment For Gordon Hayward” I cannot find the PersonName as an option to insert. I can only insert the User Row ID (I call it Payer ID). This means that it reads like “Team Assignment For 4fareirangaelrtyyys”. Any thoughts on what I might be doing wrong? ![Screen Shot 2020-06-24 at 2.24.34 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/9/9d703fd8929d7f062b524f439123e9322d6c3811.png) ![Screen Shot 2020-06-24 at 2.24.48 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/2/2138f04c5f1614730aba0d711d235ee22ff6eb70.png) ![Screen Shot 2020-06-24 at 2.36.33 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/b/bc2ff61bedb4b6701ac1dbef0a66ea94559f174c.png) ![Screen Shot 2020-06-24 at 2.42.04 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/3/342ef9b9e0e9e07f6b2baa88e13c19e8abae471b.png) ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [June 24, 2020, 10:36pm UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289/4 "2020-06-24T22:36:57Z")
Are you setting your relation to match multiple values? ---
**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:** [June 24, 2020, 10:49pm UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289/5 "2020-06-24T22:49:54Z")
Hi @ThinhDinh. Yes I was. And it looks like when I set it to match to a single single value, it magically works. Thank you! I wish there was a simpler way to figure these things out…really appreciate your help. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [June 24, 2020, 11:01pm UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289/6 "2020-06-24T23:01:51Z")
Because when your relation - lookup is returning multiple values, there can be no logical way of fitting them into a single template column. Hence the single match, as you have figured out. ---
**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:** [June 24, 2020, 11:06pm UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289/7 "2020-06-24T23:06:34Z")
I figured out…but only with your help @ThinhDinh. Thank you. ---
**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:** [June 25, 2020, 2:01am UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289/8 "2020-06-25T02:01:04Z")
@Robert_Petitto - thank you for your guidance. I got this part working now and would not have been able without your help. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [June 25, 2020, 2:04am UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289/9 "2020-06-25T02:04:56Z")
Hi Fassil, in credits to Robert, please re-assign the solution to his link so that people who search for this can see it at the top of the post instead of my answer, which is just a minor problem in your case 😄 ---
**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:** [June 25, 2020, 2:08am UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289/10 "2020-06-25T02:08:13Z")
> [@ThinhDinh](#): > > solution Will do, @ThinhDinh. Thanks. ---
**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:** [June 25, 2020, 2:25am UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289/11 "2020-06-25T02:25:37Z")
Marvelous! Glad to have helped! ---
**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:17pm UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289/12 "2020-07-09T23:17:58Z")
Hi @Robert_Petitto. Related to your above solution, I wonder if you had any insight as to how to address the following problem. When users fill submit information via a Form to sheet A, it results in a (multiple) Relationship value (that I am tracking via a Lookup in sheet B) being incremented by 1. I would like to set a visibility condition that tracks this such that when the Relationship value is “X” the component does not show. But if the Relationship Value becomes “X+1” (which happens when someone submits the Form) it does show. Any thoughts on how I can do this? ---
**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:** [July 10, 2020, 3:41am UTC](https://community.glideapps.com/t/how-to-design-choice-component-so-as-not-to-include-an-option-that-has-already-been-selected-in-the-past/11289/13 "2020-07-10T03:41:03Z")
You’d probably want to create a multiple relation in your user profile table To your form submission. In your user profile Table that does a Rollup Of this relation to get the count of form submissions. This now becomes a user profile column that you can use anywhere in the app. Hide if count is 1, for example.