Well a many-to-many relationship is first defined in the data structure. So if an Order can have many Items, and an Item can be involved in many times of Orders, that is usually defined as a third table or junction table like Order_Items. In AppSheet, you would just add all three tables to your app and set up the correct ID columns to a "ref" data type in the junction table Order_Items and point them to their correct tables. AppSheet handles displaying those related records automatically using related lists and you can add them as a "column" to any of your views in AppSheet.
@FiggyCricket I want to build app with many to many relationships. So this junction table should look like this? Unique id, order id, item id My current app is in glide now, it's for running event, si every Saturday we make a running event that can be attended by many runners, and runners can attend many events.
Can you show how to properly create a many-to-many relationship via the junction table in AppSheet?
Well a many-to-many relationship is first defined in the data structure. So if an Order can have many Items, and an Item can be involved in many times of Orders, that is usually defined as a third table or junction table like Order_Items. In AppSheet, you would just add all three tables to your app and set up the correct ID columns to a "ref" data type in the junction table Order_Items and point them to their correct tables. AppSheet handles displaying those related records automatically using related lists and you can add them as a "column" to any of your views in AppSheet.
@FiggyCricket I want to build app with many to many relationships.
So this junction table should look like this?
Unique id, order id, item id
My current app is in glide now, it's for running event, si every Saturday we make a running event that can be attended by many runners, and runners can attend many events.
How do I get the second table that "looks up" to update its values when the first table is edited?