🆕 Deleting multiple rows from a delete action

[Jeff_Hager]

I have a boolean column that is simply set to ‘true’. That is the column I use to create a relation to the table that has the rows I want to archive (delete in your case). It works for me because I have a single row, but if you have multiple rows, then I think you could also use a template column that simply returns ‘true’, or create a dummy IF column that always returns ‘true’.

I go into more detail about it here:

Auto Archiving, Sanity Check, Reusable Forms, etc

I wanted to share a few techniques that I just implemented in my app. A little background…I’m building a process in my app that will replace the email address with a template value. What it does is replace user@email.com with ARCHIVE-user@email.com. The email column is a row owner column. Once ARCHIVE is appended to the email, it becomes an unowned row and is permanently hidden from the app. I’m doing this in an effort to speed up my app by hiding data that’s more than 2 years old. Unowned…

As a simple test before you commit to deleting a bunch of rows, maybe change your relation to a single relation to make sure it’s linking to the correct row and have it delete one row at a time. My app is a little different. I don’t delete rows, but I change the row owner email, so it becomes unowned. Eventually I will manually delete the archived rows.