# Relationships

**URL:** <https://community.glideapps.com/t/relationships/68448>\
**Category:** Ask for Help\
**Created:** [December 7, 2023, 7:05am UTC](https://community.glideapps.com/t/relationships/68448 "2023-12-07T07:05:54Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Si\_Gal](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/si_gal/32/79433_2.png) [@Si\_Gal](https://community.glideapps.com/u/Si_Gal)\
**Post date:** [December 7, 2023, 7:05am UTC](https://community.glideapps.com/t/relationships/68448/1 "2023-12-07T07:05:54Z")

</div>

I am a long time Airtable user but am considering using Glide Tables for my apps. I understand that relationships in Glide works by matching items in a column from one table with items in another table and how the relationship is formed. However, what I can’t work out is maintaining that relationship when something changes.

For example. Companies have Contacts and Company Name is matched to multiple Contacts. But what happens if I change change the name of the company? The matching no longer works as because the company name isn’t updated in the contacts table.

Is there a way to create a 2 way link so that data changes are reflected on both side like in Airtable or so I have to do an action to find all the row items that match the old compnay name, and updates them with the new name?

---

<div class="post-metadata">

**Author:** ![Pratik\_Shah](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/pratik_shah/32/12416_2.png) [@Pratik\_Shah](https://community.glideapps.com/u/Pratik_Shah)\
**Post date:** [December 7, 2023, 7:15am UTC](https://community.glideapps.com/t/relationships/68448/2 "2023-12-07T07:15:12Z")

</div>

Hey, I am also Airtable user since long. I have also been using Glide since last 3 years. I understand that creating a relation in Glide and creating Linked records in Airtable are completely different.

In Glide, you need to use **Row ID** of each row and create a relation using Row ID. That way, even though you change the name of Company, relation will still be there.

> **[Row ID Column | Glide Docs](https://www.glideapps.com/docs/row-id-column)**
>
> Generate unique IDs for your rows.

In case of Airtable, it creates unique id (record id) automatically.

---

<div class="post-metadata">

**Author:** ![Si\_Gal](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/si_gal/32/79433_2.png) [@Si\_Gal](https://community.glideapps.com/u/Si_Gal)\
**Post date:** [December 7, 2023, 8:15am UTC](https://community.glideapps.com/t/relationships/68448/3 "2023-12-07T08:15:05Z")

</div>

Ah… fantastic, this is the missing piece of the puzzle I’ve been looking for

---

<div class="post-metadata">

**Author:** ![Si\_Gal](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/si_gal/32/79433_2.png) [@Si\_Gal](https://community.glideapps.com/u/Si_Gal)\
**Post date:** [December 7, 2023, 10:01am UTC](https://community.glideapps.com/t/relationships/68448/4 "2023-12-07T10:01:14Z")

</div>

This is great but I have a question. Again I am used to Airtable creating a relationship on both sides so that in the Company table I have a 1 to many relationship and a in the contacts tabl there is a 1 to 1 relationship.

I can see that this isn’t the case for Glide. I’ve now created a Organisations Table and a Projects Table. I’ve created a 1 to many relationship in the organisations Table using the Row Id as you recomended as one organisation will have multiple projects. When I then try and do a look up from Projects table for the Organisation Name, it brings all of the name with it.

I’ve fixed this by adding a relationship from the Projects table to the Organisations table.

Is this best practice? I want to do it right from the start

---

<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:** [December 7, 2023, 10:13am UTC](https://community.glideapps.com/t/relationships/68448/5 "2023-12-07T10:13:43Z")

</div>

Yes, this is best practice. If you need to have a relation in both tables, then it will be two separate relations. If your want a Lookup column to specifically pull data from a relation, then yes you need to have a relation for it to pull from.

---

<div class="post-metadata">

**Author:** ![Si\_Gal](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/si_gal/32/79433_2.png) [@Si\_Gal](https://community.glideapps.com/u/Si_Gal)\
**Post date:** [December 7, 2023, 10:18am UTC](https://community.glideapps.com/t/relationships/68448/6 "2023-12-07T10:18:33Z")

</div>

Great thanks

---

<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:** [December 14, 2023, 10:18am UTC](https://community.glideapps.com/t/relationships/68448/7 "2023-12-14T10:18:35Z")

</div>

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