Yeah, this is a recent regression. Glide team is aware of it and I believe a fix is on the way.
In the meantime, one thing I found is that you can select multiple rows and just keep hitting the delete key and get rid of them one by one. (Yeah I know that’s not a lot of help if you have 4000 rows to remove).
Yeah, if it’s not referenced anywhere then the rows shouldn’t count.
If you’d like to turn it into a sort of FIFO log, there is a trick that can be used to automatically delete the oldest rows. All you need to do is use a Single Value or a Rollup to identify the oldest row in the table, then build a Single Relation to that row. Then you can include a Delete Row step in your Add Row sequence that deletes that oldest row. The end result will be that you’ll have a rotating log with a fixed number of rows.
Yes I have that in other places in the app but the issue is I need to clear these 4000 rows and maybe i could set that up once the table is down to 100-200 rows.
By the way i just finished manually deleting all rows (kept my finger on the delete button)… closed app and opened again to find the count still at 2900 … so i guess even that doesn’t work unless you give time for Glide to delete before you click again.
Seems like mass deleting multiple rows is functioning again in the glide editor.
However, i would advise anyone using it to avoid any further actions in Glide after deleting and to reload app to confirm. It doesn’t work well for a big number of rows. I tried a couple thousand rows at once and although they disappeared from the editor. On reload, most of them appeared back again. But still its working, unlike before where it was deleting 1 row (the first selected) only.