# Update Relation based on Collection choice (not a choice component) **URL:** \ **Category:** Feature Requests\ **Created:** [June 7, 2020, 7:31pm UTC](https://community.glideapps.com/t/update-relation-based-on-collection-choice-not-a-choice-component/10462 "2020-06-07T19:31:25Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Naos\_Wilbrink](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/naos_wilbrink/32/769_2.png) [@Naos\_Wilbrink](https://community.glideapps.com/u/Naos_Wilbrink)\ **Post date:** [June 10, 2020, 12:26pm UTC](https://community.glideapps.com/t/update-relation-based-on-collection-choice-not-a-choice-component/10462/4 "2020-06-10T12:26:06Z")
> [@Jeff\_Hager](#): > > A zap would work to, but it’s just more overhead to get it set up initially. Once set up, then it would be easy to implement on a list I think. Yeah I tried a ZAP,… I found it very slow. So I’d use it more for data that doesn’t require an immediate app in app change,… like sending out daily digest mails. Or a user requested “Give me my data” request. > [@Jeff\_Hager](#): > > and set up your relation from the user profile to the challenge sheet using email. But nothing would stop them from selecting multiple checkboxes, unless you are ok with that. Still thinking about this one,… --- _[View the full topic](https://community.glideapps.com/t/update-relation-based-on-collection-choice-not-a-choice-component/10462)._