I want to know an automation where deleting a table row will also delete other table rows.

[suzukixxx]

When a user enters a meeting schedule into the meeting table, the same meeting schedule is automatically entered into the linked Google Calendar table.
It worked fine so far.
However, when you delete a row in this meeting table, the appointment will not disappear from the calendar table.
I ended up deleting all client schedules while experimenting with automation!!
I am writing this with great fear right now. I would like to know the correct action.

The settings I failed to set the event as
"data change", "delete only", "meeting table",
Set the process settings to
"run a data action" and "schedule table"
I set "= schedule table [Row ID]" and "delete". Of course, this will remove all schedules from the schedule.
I'm too scared to report it to my client yet.

[Marc_Dillon · Accepted solution]

Oops!

Your setup description is not very clear, but are you saying for the "Referenced rows" section, you entered schedule table [Row ID] ? That would indeed delete the entire "schedule table" table. You need to use a FILTER expression to look up the exact record(s) to delete, to match the one you just deleted. Something like:

FILTER( schedule table , [ref-column] = [_THISROW] )

[suzukixxx]

thank you!
Solved my problem a bit. Setting the process settings to "run action on rows" and putting the formula you gave me in Referenced rows worked.
But new questions arose.
A bot that added a row to table A (meetings table) also added a row to table B (google calendar) worked.
And thanks to you, deleting rows in table A also deletes rows in table B.
But I couldn't figure out how to update the information in the B table if I change the A table.
So, Adds only and delete only worked, but I don't know how to make updates only work.
do you know how to solve that?

[Marc_Dillon]

https://www.googlecloudcommunity.com/gc/forums/searchpage/tab/message?advanced=false&allow_punctuati...

[suzukixxx]

Thank you for your reply. I understood that there are various approaches. But I found them all difficult. I'll read through this a little further.

[Koichi_Tsuji]

AppSheet does not provide a native and easy way to update the row in the row(s) in another table.   It is said that the add new row to another table action may suffice, but it is not an absolute solution.

[suzukixxx]

thank you for your reply. I understand that. As a result, I think it is necessary to create three separate actions for adding, deleting, and updating.
Adding and deleting worked fine, but I still don't know how to update. I also thought that the fact that another table was a google calendar made the situation complicated.
The function I am currently challenging is that when table A is updated, a row is added to table B (Google calendar), and the old row number of table B is selected and deleted. But this is not yet finished.
Specifically, the contents are as follows.

but this doesn't work. The description is specified because there is no column for entering the ID associated with the A table on the Google Calendar side.

辻さん、お返事ありがとうございます。
旧フォーラム等、大変参考にさせて頂いています。
初心者ゆえ、もう少し上達してからDOJOに参加しようと思っています。
上記英文はGoogleトランスレートで変換したものですので、
念のため日本語も載せておきます。

追加、削除、更新の３つを別アクションで作成する必要があると考えています。
追加と削除に関しては上手く機能しましたが、更新の方法が未だにわかっていません。それは別テーブルがgoogleカレンダーである事が状況を複雑にしているとも思いました。
今チャレンジしている機能は、Aテーブルが更新がされるとBテーブル（グーグルカレンダー）に行が追加され、Bテーブルの古い行番号を選択し削除する、という機能です。しかしこれはまだ完成していません。
具体的には上記添付写真のような内容です。

しかしこれは機能しません。descriptionを指定しているのはグーグルカレンダー側にAテーブルと紐づけるIDを入力するカラムが無いためです。これは無理矢理な感があるなと理解しながら苦肉の策ですが、他にもっとスマートな方法があるはずと試行錯誤している段階です。

[suzukixxx]

こちら解決できました。
追加と削除が機能していたので２つを組み合わせて更新のオートメーションが完成しました。
ただ、やはり少し無理矢理な感はある（特にテーブルAからテーブルBを紐づける方法）ので応急処置的な状態で終わっています。
とにかくお答えいただきありがとうございました。

[suzukixxx]

I was able to resolve the issue with this topic and the associated update issue.
The first idea that came to my mind was that the combination of working "add" and "delete" would complete the "update" automation. But at the time, I assumed that after deleting a row, I wouldn't have the information to add another row.
But in practice everything worked fine.