Here is how I have implemented putting a permission on deleting. For regular users who are not an admin level I remove the ability to delete.
Then I make a checkbox on the parent record called [Request Deletion].
Then I make a pipeline or a automation which obviously will run under its own permissions and it will be triggered when the check box is checked and it will do the dirty deed to delete that record.
I would then make a formula URL button to check the checkbox but only present that button to the users if the conditions you require are true. You could also put belt and suspenders on that by making sure that the automation or pipeline did not delete the records if your condition or not true.
Pending on the user experience you want you could decide if you want to check the chat box with the formula URL button which would check the checkbox and land the user somewhere else. Alternative is that the user check the checkbox but of course the record will immediately redisplay to the user because the record will display quicker than the automation or pipeline will fire. That may be a good enough experience, or else you might want to make a URL formula button which would check the checkbox on the land the user on the dashboard or table homepage for example
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.commark.shnier@gmail.com
------------------------------
