"Single Value" remains after all columns have been "Cleared" on an entire row

I’m clearing all available columns in a row but a few Single Value columns will not go away. I’ve also cleared all blank cells in case there was some ghost info in there.

I’m trying to get the rows to completely clear themselves out after a task is 100% complete. Any advice out there?

My app’s URL: mgm.nowait.today

Why do you have 5 seemingly empty rows at the top? Is it a syncing issue?

When an item on the list is completed, I have an action that clears all available fields. So you’re looking at old rows that will not disappear because clearing all rows doesn’t auto delete a row. I guess I have to wait for a “delete row” action.

Do you have rowID in those rows?

No… I have in the past and got rid of it in this solution but it didn’t help the problem.

Can you try duplicating the app and point it to the same sheet to see if the problem persists?

did you put any “” there? with arrayformula? it will keep a value

It’s a Glide Sheet. All I know is the “Single Value” and “Template” columns don’t disappear when everything else is cleared…

It’s a Glide Sheet

just delete them in google sheets and add new ones

I don’t think you understand the issue. This is a glide sheet. All values are cleared via action. Single values and templates remain though nothing else in the row is there.

This is not a Google sheet and my app sees about 1000 entries per week day. Manually deleting rows in the glide editor is going to be a nightmare.

1 Like

I suppose since a Glide table more mimics an actual database instead of a spreadsheet…then that means a row is a row, whether or not all the columns are empty. Normal databases don’t have “empty” rows that are ignored. A row either exists or it doesn’t. Glide’s solution of ignoring empty rows in a spreadsheet is probably more of hack in a sense because new sheets typically start out with 1000 empty rows and it would be a lot of overhead for glide to process those empty rows all the time. A Glide table, on the other hand, is different because it’s more like a normal database and the only rows that exist are the ones that were created either manually or programmatically. To remove a row, you need to actually delete it.

In my opinion, I would expect this kind of behavior from Glide Tables. In my experience with databases, you need to issue a delete command to delete a row. Simply clearing values does not destroy the row. In fact, in most indexed databases, you would run the risk of duplicate keys due to the indexed keys of rows matching each other and causing conflicts. Not so much here, as the table is either not indexed, or any indexed keys are hidden from our view. Point being that glide tables are most likely quite a bit different behind the scenes compared to spreadsheets.

I more agree with your statement that we should have a delete action instead of automatically deleting rows based on cleared columns.