# Bringing value from one table to another like INDEX MATCH would do

**URL:** https://community.glideapps.com/t/bringing-value-from-one-table-to-another-like-index-match-would-do/70246
**Category:** Ask for Help
**Created:** [January 30, 2024, 11:31am UTC](https://community.glideapps.com/t/bringing-value-from-one-table-to-another-like-index-match-would-do/70246 "2024-01-30T11:31:50Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Mathieu\_Gomez](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mathieu_gomez/32/61057_2.png) [@Mathieu\_Gomez](https://community.glideapps.com/u/Mathieu_Gomez)
#### Post date: [January 30, 2024, 11:31am UTC](https://community.glideapps.com/t/bringing-value-from-one-table-to-another-like-index-match-would-do/70246/1 "2024-01-30T11:31:51Z")

</div>

Hello  
Ok so I have a user table where it tells me whether the user is a CLAIMANT or a DEFENDANT in a case.  
I then have a case table - listing all the open cases.  
In this table case, I’d like to list who the claimants and defendants are. I think in Excel I would do that with a INDEX MATCH formula. But I have not been able to find a solution to do this in Glide.  
Thank you

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/5/e5d0ed63d93fd079c4572898fbc818ef67af0435.png)  
 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/5/5/55219c713bf39a341c217a5dc302f01221f78833.png)

---

<div class="post-metadata">

### Author: ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)
#### Post date: [January 30, 2024, 12:00pm UTC](https://community.glideapps.com/t/bringing-value-from-one-table-to-another-like-index-match-would-do/70246/2 "2024-01-30T12:00:02Z")

</div>

You’ll need 4 columns in your Cases table. Two Query columns, and two Single Value columns.

- queryClaimant: A Query column that targets your Users table and applies the following filters:  
– CaseID is This row → CaseID  
– Role is Claimant
- queryDefendant: A Query column that targets your Users table and applies the following filters:  
– CaseID is This row → CaseID  
– Role is Defendant
- svClaimant: A Single Value column that targets the first Query column and takes the first Name
- svDefendant: A Single Value column that targets the second Query column and takes the first Name

---

<div class="post-metadata">

### Author: ![Mathieu\_Gomez](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mathieu_gomez/32/61057_2.png) [@Mathieu\_Gomez](https://community.glideapps.com/u/Mathieu_Gomez)
#### Post date: [January 30, 2024, 1:55pm UTC](https://community.glideapps.com/t/bringing-value-from-one-table-to-another-like-index-match-would-do/70246/3 "2024-01-30T13:55:30Z")

</div>

Thank you. So I need to use Query so I can use the ‘filter’ feature - and not use relation and lookup.  
Thanks for your help.

---

<div class="post-metadata">

### Author: ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)
#### Post date: [January 30, 2024, 2:15pm UTC](https://community.glideapps.com/t/bringing-value-from-one-table-to-another-like-index-match-would-do/70246/4 "2024-01-30T14:15:04Z")

</div>

Yes, that’s correct.  
Before we had the Query column, you would have needed Template-\>Relation-\>Lookup.  
The Query makes it easier.

---

<div class="post-metadata">

### Author: ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)
#### Post date: [February 6, 2024, 2:15pm UTC](https://community.glideapps.com/t/bringing-value-from-one-table-to-another-like-index-match-would-do/70246/5 "2024-02-06T14:15:25Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.