# Relational data in the app should use Unique Key / Row ID as choice value

**URL:** <https://community.glideapps.com/t/relational-data-in-the-app-should-use-unique-key-row-id-as-choice-value/7181>\
**Category:** Feature Requests\
**Created:** [April 16, 2020, 10:23pm UTC](https://community.glideapps.com/t/relational-data-in-the-app-should-use-unique-key-row-id-as-choice-value/7181 "2020-04-16T22:23:21Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![j.h.scheufen](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/j.h.scheufen/32/1379_2.png) [@j.h.scheufen](https://community.glideapps.com/u/j.h.scheufen)\
**Post date:** [April 16, 2020, 10:23pm UTC](https://community.glideapps.com/t/relational-data-in-the-app-should-use-unique-key-row-id-as-choice-value/7181/1 "2020-04-16T22:23:21Z")

</div>

I have the following challenge which prevents me from taking the app to the next level and grow the user base: I need users to establish relationships between each other and other entities (e.g.) groups and the most sensible way to achieve a nice user experience is to use the Choice selection.

The problem is that the Choice component does not differentiate between the display label and the value stored in the sheet. It’s the same. So, when I display a range of other users I display their names in the selection and the name is what gets stored in the underlying sheet.  
Now, if the user changes their name, the referential integrity of that relationship is broken.

Glide should allow more configurability in the Choice component to select which value is used for display in the list (Name) and which value gets stored upon selection (e.g. UUID). Just like a choice component in HTML that distinguishes between the label and the underlying value that gets transmitted.

If there are any ideas how to work around this, I’d be all ears, but I was not able to conceive of a solution to this problem.

Thanks!

---

<div class="post-metadata">

**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:** [April 16, 2020, 10:34pm UTC](https://community.glideapps.com/t/relational-data-in-the-app-should-use-unique-key-row-id-as-choice-value/7181/2 "2020-04-16T22:34:20Z")

</div>

Both @Jeff_Hager and I have requested this too.

Upvote “Separate display vs sheet values in Choice”

> **[Feature Requests](https://features.staging.glideapp.io/)**
>
> Feature requests for Glide Apps

---

<div class="post-metadata">

**Author:** ![j.h.scheufen](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/j.h.scheufen/32/1379_2.png) [@j.h.scheufen](https://community.glideapps.com/u/j.h.scheufen)\
**Post date:** [April 16, 2020, 11:57pm UTC](https://community.glideapps.com/t/relational-data-in-the-app-should-use-unique-key-row-id-as-choice-value/7181/3 "2020-04-16T23:57:17Z")

</div>

Done. Thanks, Robert!

---

<div class="post-metadata">

**Author:** ![j.h.scheufen](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/j.h.scheufen/32/1379_2.png) [@j.h.scheufen](https://community.glideapps.com/u/j.h.scheufen)\
**Post date:** [May 12, 2020, 4:32am UTC](https://community.glideapps.com/t/relational-data-in-the-app-should-use-unique-key-row-id-as-choice-value/7181/4 "2020-05-12T04:32:44Z")

</div>

I just found out today that this was now implemented and is already available in the app! No announcement?

---

<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:** [May 12, 2020, 5:06am UTC](https://community.glideapps.com/t/relational-data-in-the-app-should-use-unique-key-row-id-as-choice-value/7181/5 "2020-05-12T05:06:06Z")

</div>

> [@new Choice now has a 'Display as' property](https://community.glideapps.com/t/choice-now-has-a-display-as-property/8544):
>
> This allows you to display choices to the user that correspond to different underlying values. For example, the user could choose a Product Name (e.g. Kitty Litter), but the value is actually the Product Id (e.g. 687y9878g). In our Template Approval app, I can choose between canned responses. The choice items are displayed by their Code, but the values are long Message values:

---

<div class="post-metadata">

**Author:** ![j.h.scheufen](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/j.h.scheufen/32/1379_2.png) [@j.h.scheufen](https://community.glideapps.com/u/j.h.scheufen)\
**Post date:** [May 12, 2020, 12:10pm UTC](https://community.glideapps.com/t/relational-data-in-the-app-should-use-unique-key-row-id-as-choice-value/7181/6 "2020-05-12T12:10:18Z")

</div>

Thanks, @Jeff_Hager! I missed that in announcements.
