# Matched pairs of data

**URL:** <https://community.glideapps.com/t/matched-pairs-of-data/26805>\
**Category:** Ask for Help\
**Created:** [May 14, 2021, 6:25pm UTC](https://community.glideapps.com/t/matched-pairs-of-data/26805 "2021-05-14T18:25:17Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![BlakeWS](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/blakews/32/24377_2.png) [@BlakeWS](https://community.glideapps.com/u/BlakeWS)\
**Post date:** [May 14, 2021, 6:25pm UTC](https://community.glideapps.com/t/matched-pairs-of-data/26805/1 "2021-05-14T18:25:17Z")

</div>

Glide Tables: Is there a way to create matched pairs of data, like key & value?  
If/Then/Else seems really terrible for this once you get many items to pair up, and Lookups don’t seem to work well for this.  
How are people handling product/price pairings in their stores?

---

<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 14, 2021, 6:37pm UTC](https://community.glideapps.com/t/matched-pairs-of-data/26805/2 "2021-05-14T18:37:10Z")

</div>

Do you mean like a relation to link the keyd and a lookup to get the value from the relation?

---

<div class="post-metadata">

**Author:** ![BlakeWS](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/blakews/32/24377_2.png) [@BlakeWS](https://community.glideapps.com/u/BlakeWS)\
**Post date:** [May 14, 2021, 6:55pm UTC](https://community.glideapps.com/t/matched-pairs-of-data/26805/3 "2021-05-14T18:55:31Z")

</div>

Ahhh I think I got it now, I was having a mental block about how I was storing the data for all my choice components. I had them all in one table like I had done for other apps, but it’s not going to work this time. I have to split that single table into multiple tables that contain the key/value pairs. Thanks

---

<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 14, 2021, 6:57pm UTC](https://community.glideapps.com/t/matched-pairs-of-data/26805/4 "2021-05-14T18:57:41Z")

</div>

I would think you could still use a single table. I have a table that contains a bunch of random different choice data and key/value pairs. You just need to set up each relation to the correct key for the related data and you should be fine.

Just a small clip of my sheet:

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/3/f3a3b0539da6c3f34178507d53d8d18cf0fdd6b1.png)

---

<div class="post-metadata">

**Author:** ![BlakeWS](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/blakews/32/24377_2.png) [@BlakeWS](https://community.glideapps.com/u/BlakeWS)\
**Post date:** [May 14, 2021, 9:06pm UTC](https://community.glideapps.com/t/matched-pairs-of-data/26805/5 "2021-05-14T21:06:29Z")

</div>

Okay, I remembered why I was having to jump through some hoops and things weren’t going to work out in the regular way. I hadn’t worked on this app for a couple of weeks. I’m fighting the “User-first” style of app, whereas I don’t want the User to sign-up at the beginning, but I want User-specific content.

I’m not able to do my relations and lookups in the same table as where my choice component writes to as they can’t be user-specific, see the screenshot.

![Visy · Glide - Google Chrome 2021-05-14 at 1.53.50 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/optimized/3X/8/c/8cf6e019ad29f216f29f775c1e4ab63be0d03671_2_690x312.jpeg)

I have to use an intermediate table to do the calculations I want, but then the relations and lookups don’t work. I’m using a UID to keep the continuity between tables, and only the tables with user-specific columns are linked to tabs in the app. So now I’m trying to find the best way to take the key input of a choice component, reference a table for a key/value pair, and then bring the value back haha. I think the separate tables for the key/values will do it. Trying to avoid user sign-ups is fun!

![Visy · Glide - Google Chrome 2021-05-14 at 2.03.21 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/optimized/3X/c/3/c34457acfe93ea3fb2e0623a18d146a24af17f15_2_690x312.jpeg)

---

<div class="post-metadata">

**Author:** ![NoCodeAndy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodeandy/32/62530_2.png) [@NoCodeAndy](https://community.glideapps.com/u/NoCodeAndy)\
**Post date:** [January 17, 2024, 4:52pm UTC](https://community.glideapps.com/t/matched-pairs-of-data/26805/6 "2024-01-17T16:52:18Z")

</div>


