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?
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.
In case of Airtable, it creates unique id (record id) automatically.
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
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.