This is a feature lacking that gives a weird and bad UX.
When it exists a delete link on table lines, deleting works very smoothly.
But most other cases, like having a Delete link at the bottom of an Edit Form, leaves the user in No man’s land. All the form fields disappear, and there are absolutely no way to inform the user on what to do or where to go. It’s like Hello?
So I propose that a similiar Submit Rules module for SUBMITING a Form should be available for DELETING.
Anyone having this No man’s land cases?
TBH I never give users the ability to hard delete records. As there is no audit trail it’s a risk I prefer to avoid. I do understand the UX challenge though.
Archive, Restore and Soft Delete - Knack Database
Due to the inability to batch delete from the Live app I try and get users to “hard” delete whenever practicable which causes the problem outlined above by Michael, as Carl says in his very clear and concise video, keeping the record and marking it as deleted/archived keeps an audit trail and gives us much more control over the process, so yes some control over the delete option would be very welcome even if its just to place the confirmation box next to the record that is being deleted would be an improvement.
After clicking Delete, there is always a pop-up message that ask for confirmation. Probably a security predefined by Knack.
Just seen again your video tutorial @CarlHolmes .
Soft Delete (trash) is a good way to delete it on the client side and have a backup if needed.
In my use-case I only gave access to hard delete to the Admin role.