First, I would ask if it's
absolutely necessary that the users should be able to actually delete the records. Unless the table houses hundreds of thousands of records and space on the table is at a premium, I generally recommend that only Management or Administrators are able to fully delete records. Instead, I put a process in place that allows users to recommend a record for "deletion" and then mark the record as "Inactive" or "Deleted" and use that field as a filter so that users can no longer access it, but it remains in the system.
If you DO need to actually remove the record, but want to keep an archive of deleted records, I would still do the same process as above, but would add in two Automations or Pipelines. The first automation would make a copy of any record marked for deletion and then mark the original that a copy had been created. The second automation would actually delete the records. I typically set these up so that there is a period of about 48 hours between when the record is originally marked to when it is deleted. Something like this:
- Day 1 - Record is flagged for Deletion
- Day 2 - Records flagged as Deleted Yesterday are copied to the Archive and flagged as having been Archived (Automation 1)
- Day 3 - Records flagged as Archived Yesterday are deleted (Automation 2)
Offsetting the timing of these automations gives the users / management to review these for any errors and undo the deletion if necessary.
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quick Base Solution Provider
Atlanta GA
404.800.1702 /
http://datablender.io/------------------------------
