I’m not experienced using a Google Calendar as a data source for an AppSheet table. Conceptually, one of the following is likely an appropriate approach.
Don’t use separate tables to begin with. If necessary, create multiple views of the same table.
If you use separate tables, ensure that one references the other. Then, you could use dereference expressions to accomplish needs like replicate redundant columns (e.g., Start, End) and utilize a related rows column for an action’s Referenced Rows property.
I really thank you. I could make action to edit Google calendar row when related spreadsheet changes. But I still cannot do it automatically.
First, I made action to add row from spreadsheet to Google calendar. Since I could not edit Row ID, I added Unique ID in spreadsheet to Location in Google calendar.
When new row in spreadsheet added, new row in Google calendar also should be added. Then existing row in spreadsheet is edited, related row in Google calendar also should be edited automatically.