Forum Discussion
- EvanMartinezQuickbase StaffHi Dean,
Deleting records is an option that is now available directly in an Automation. So using the same Automation logic you might use to trigger a record being added, changed, or copied to another table you can also trigger a record being deleted. For example when a Project record is marked as cancelled in the Status Field and the Authorization checkbox is checked it could trigger an Automation to delete that record as one of the steps. You can even set up a step first to copy that record to a Project Archive table first before running the delete if you wanted to capture all those records in case of accidental deletion. The users then wouldn't need to be given Delete permissions, the builder of the Automations would just need delete permissions. I do caution that automating deletions like that are something you want to be careful of as when data is deleted in QB it is removed unless you have a step in place to capture it first.
Alternatively, to kick of a script that would not be something that Automations can do alone. It is possible to set up an Automation that can trigger a Webhook out to a service with a script or some other way to bring a script into play but our Automations do not have a step to specifically call a script built in. - ChayceDuncan2Qrew CadetEvan's points above are definitely the route I would suggest if your end goal is primarily around deletions - but if you're still looking for other options - a couple options might be using Google Scripts (here is an community post and reference to a Kirk Trachy youtube video about using it for Imports). Another option is using AWS Lambda - probably a little bit more robust but definitely could do what you're looking for.
Chayce Duncan | Technical Lead
(720) 739-1406 | chayceduncan@quandarycg.com
Quandary Knowledge Base