Forum Discussion
QuickBaseCoachD
8 years agoQrew Captain
Here is another approach. Make an Automation to delete the record when a certain checkbox is checked. The automation run under the Permissions authority of who created it (actually who last modified it).
So sort of by remote control, the user can request the automation to fire.
Then you have infinite control over who can see or edit that checkbox field and even if the user does not have permissions to delete record, that can "phone a friend" (if you remember that TV show "Who wants to be a millionaire"), and ask them for help.
So sort of by remote control, the user can request the automation to fire.
Then you have infinite control over who can see or edit that checkbox field and even if the user does not have permissions to delete record, that can "phone a friend" (if you remember that TV show "Who wants to be a millionaire"), and ask them for help.
- Laura_Thacker8 years agoQrew CommanderMark - this is a nice approach too. Since Automations is new; it is interesting to see all the different ways in which this feature can be used to replace older clunky work arounds /mechanisms. Personally, I still have concerns over accidental deletion of records, even by Administrators - which I have sadly seen too often.
- QuickBaseCoachD8 years agoQrew CaptainThe other approach that i used to use was a webhook to delete the single record. But there is some 'coding" syntax involved in setting up a webhook, so I would not try to guide someone though that coding on this forum.
- _anomDiebolt_8 years agoQrew EliteI can't for the life of me understand why there is this aversion to coding.
Even psychonaut Terence McKenna realized everything is code: - Laura_Thacker8 years agoQrew CommanderAfter building a few automations myself; I am sure many users will take that route instead of Webhooks, where appropriate.