Quickbase Integration Set Up for DSR Automation

With the Transcend Quickbase integration, you can fulfill Access DSRs directly against a Quickbase application by running Quickbase queries with our custom JSON payload for the access data actions on each datapoint.

The first step to setting up DSRs against a Quickbase application is creating the datapoints in the data silo that should be queried. We typically recommend creating a datapoint for each table in the application that stores personal data (or any collections you want to action DSRs against). For example, let's say there is a table called Chat History that contains all the messages sent back and forth from a customer. You could create a datapoint for Contacts in the data silo and enable the specific data actions needed. If you're using Structured Discovery, you can enable the Datapoint Schema Discovery plugin to create the datapoints for you automatically.

Pro tip: Check out the Transcend Terraform Provider for options on managing data silos and data points in code.

Create a datapoint in the Quickbase Integration

For each data action enabled for a datapoint in the Quickbase data silo, you can define a JSON payload that will execute a database operation. Using the previous Contacts example, let's say you want to enable the Contacts datapoint to support access/right to know requests. With the “access” data action enabled, you can define a specific JSON payload that executes the request to find the Contacts for a user against the database. The next sections outline how to construct the types of queries that are supported, how to construct the custom payload, and outlines sample queries.

Define a custom query for a data action on a datapoint

Transcend’s Quickbase integration supports querying data for access/right-to-know requests. This operation Access Data Request could be actioned with a select query type.

As mentioned above, the Quickbase integration uses a custom query payload to execute queries against Quickbase tables. The parameters to be included in the payload are described below. Please note that all the parameters are required and must be included in the payload. For a more in-depth look at query options, including optional ones, please refer to the Quickbase Query for data docs.

  • select: the field identifiers to select
  • from: the table identifier
  • where: the filter, using the Quickbase query language, which determines the records to return.

    If the where parameter is omitted, the query will return all records in the table so make sure this is defined to filter for results only relevant to the user it's intended for. See Query Template Variables below.

Sample Payload for Access Request
{
  "select": [6, 7, 8, 17],
  "from": "buxbxbwix",
  "where": "{[email protected]"
}

We also support a few template variables that can be used inside your query.

  • {{identifier}} — This replaces the template with the identifier (i.e. email)

ex. to query for a user with an email identifier, then the query should look like,

{
  "select": [7, 8, 6, 17],
  "from": "buxbxbwix",
  "where": "{17.EQ.{{identifier}}}"
}

The above query selects fields with identifiers 7, 8, 6, and 17 from table with identifier buxbxbwix where field 17 is equal to the identifier, which can be a value like email.

OSZAR »