Data Logs & undo row deletion

Hey guys, I am using Coda as a mini ERP x CRM for my company. I appreciate the flexibility and modularity and was able to put something together in less than 4 months; something that would have taken us probably over a year to build ourselves.

However, there are a few things that really bugged me. Biggest ones are absence of data logs & ability to undo deletion.

On data logs:
I managed to create my own automation to log changes to key fields of a table, HOWEVER, it’s very costly to set up and maintain (in case I have to add new fields). Also, I cannot detect changes to a Canvas field, which is where we put our CRM notes.
So my suggestion would be: Why can’t you simply build log tables that automatically detect changes to any of the fields (all fields by default, with ability to unselect some) and trigger notifications for this. This is something that Notion can do a very good job at. I do not see how that would be so complicated.

On row deletions:
I am aware there are doc locking & page locking features (I’m on Team plan). However, sometimes, I have to allow my team members to delete rows for legitimate reasons (so I cannot toggle of the Delete rows function) and it happened a couple of days ago that somebody in my team deleted rows from a table accidentally and had NO idea until we detected a loss of some rows in our posgre table (we have set up a Postgre automation, which is accessible via Metabase). When I tried to restore the doc to an earlier version before those deletions took place, I had to contact Customer Support team, which only works Mon-Fri; and, so, now it’s Monday (I’m in Asia) and we’re not able to use Coda for one full day untl they do the restoration. I’m aware I could just copy the earlier version but all my packs would break and we use lots of packs, and so this would take forever to do. So a couple of suggestions on this:

  • Why don’t you allow user to restore to an earlier version of the doc themselves IF you’re already allowing to copy the ealrier version on their own?

  • If you can’t yet build logging for all table changes (as I suggested earlier), could you at least build logging for table and row deletions? Deletions are critical. We should at least be aware of them.

  • Confirmation for deletions. Deleting rows in Coda is extremely easy that it’s so scary. Can you at least build a confirmation modal for row deletions? I am finally restoring to building a Delete button that user can press after expressly confirming they want to delete it by toggling on a separate field….but it just seems like a very costly workardound that I’d have to do for every single table I have. :frowning:

Please consider these requests when you’re building the Sub-Sharing feature

Hi,

For now you can partially compensate :

Create DB Log :slight_smile: ( one col text and on col auto date created)

And buton delete on you table task for exemple :

On click : addrow(DB Log, log, your data) and delete thisrow :slight_smile:

we always provide a DELETE button that just flags the row as logically deleted.

live views are always filtered to never show these rows.

4 Likes

As @Agile_Dynamics said. Lock the table so that the user can’t delete rows, then add a delete button that changes the row’s status and hide all rows with that status from the user’s view. Remember to also have hidden columns for “date deleted” and “deleted by”.

3 Likes

An additional benefit of that method is that you can build a page with rows tagged as “deleted”. Then you can have a button to “undo” the deletion and another one to permanently delete the row (for obvious mistakes). And you can create a hidden table where you select users who should have the right to permanently delete rows. Then you can disable the “permanently delete” button for anyone who’s not on that list.

3 Likes

To generalise what the commenters before me said: “It is not only necessary to customise the system, but also to systemise the custom”.

When you get to the stage where you use Coda as a “mini ERP + CRM” it is very necessary that you have defensive code in place to protect the data in the system.

But I do agree with you on the support - office hours out of California is an insult to the large non-US community of Coda users. Probably more than half of the people that regularly comment on the community are not US based.

2 Likes

YES!! Support outside of California office hours + proper number localization + customization for the “submit” button in a form = happier non-US customers. Maybe some day…

1 Like

Thank you, I like this idea!

2 Likes

You are right. Thank you for the suggestion!

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.