Get Expert Help

Quick Base Junkie Blog

Short videos and posts to skyrocket your Quickbase skills!

Get tips in your inbox

Join the Quick Base Junkie Community email list!

Stop the madness! Prevent records from being deleted in Quickbase

advanced api api examples how to intermediate roles Jul 11, 2018

Subscribe on YouTube

We've all been there, we or someone we work with has permanently deleted data that should have been kept. Then we spend hours recreating the data, finding out who deleted it, or hoping no one will notice. In this tutorial, you'll learn that it's possible to allow users to delete records, without actually deleting them.

You may be in need of some role controls if you answer yes to any of the following:

  • Have you discovered "gaps" in your records?
  • Have you spent hours recreating deleted records?
  • Have you pleaded with your users to not delete records?

In this tutorial, I'll show you how to prevent the dreaded accidental delete. There are three things that it will cover:

  1. Identify who should have delete privileges
  2. Adjust Role settings
  3. Create a faux delete (optional)

Who's ready to save some records from the trash!


Delete button URL formula code

URLRoot() & "db/" & Dbid() & "?a=API_EditRecord&rid=" & [Record ID#] & "&_fid_24=1&rdr="& URLEncode(URLRoot() & "db/" &[_DBID_TIME_CARDS] &"?a=td")

The "fid_24" refers to the field ID for the Delete checkbox.
The "[_DBID_TIME_CARDS]" refers to the table alias, which can be found in the advanced settings of the table.

Version with an app token

URLRoot() & "db/" & Dbid() & "?a=API_EditRecord&apptoken=XXXXXXXXXXXXXXXXXXXXXXXXXX&rid=" & [Record ID#] & "&_fid_24=1&rdr="& URLEncode(URLRoot() & "db/" &[_DBID_TIME_CARDS] &"?a=td") 

You can find/add app tokens in the App Settings > App Properties > Advanced Settings > Security Options.




Feeling like a Junkie?  Subscribe Now!