---
title: "Enable updates to existing Quickbase records"
slug: "enabling-updates-to-existing-quickbase-records"
updated: 2026-09-28T06:23:24Z
published: 2026-09-28T06:23:24Z
canonical: "help.quickbase.com/enabling-updates-to-existing-quickbase-records"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.quickbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Enable updates to existing Quickbase records

When setting up a [Send to Quickbase](/fastfield/docs/set-up-a-quickbase-integration-in-fastfield-with-a-user-token) Global Workflow action, you can turn on the **Enable Updates** toggle to allow automatic updates to existing records on your Quickbase table.

This feature will overwrite data in an existing Quickbase record when the designated **Quickbase unique field** value matches the specified **FastField form field** value. All other form data will be inserted as new rows in your table.

If you do not turn on the Enable Updates toggle, *all* submitted form data will be added as new rows in your table. This could cause your table to include multiple rows for the same entity, such as a customer name, asset, or site.

By enabling updates, however, it will simply update existing details for the unique entity, instead of creating multiple entries.

## Set up in Quickbase

First, you'll need to designate the [unique fields](https://helpv2.quickbase.com/hc/en-us/articles/4570409950996-Requiring-unique-entries-in-fields-) whose rows of data you want to be updated on your Quickbase table when the corresponding FastField form is submitted. To do this:

1. Log in to Quickbase and select your app.
2. Select the table.
3. On your table page, go to **Settings** > **Fields.** Here you can see all the fields in your table. ![Fields list in the Quickbase table settings](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/21001372513293?sv=2026-02-06&spr=https&st=2026-10-30T00%3A38%3A33Z&se=2026-10-30T01%3A38%3A33Z&sr=c&sp=r&sig=kmUCWsPnubiMop0wzpelPhlZDaKqEmvMnqAZuUdOEok%3D)
4. Select a field that you want to designate as *unique*. This sets it as a unique identifier (unique field) for the records to be updated when matched with a form field.![Must be unique option in the Quickbase field properties](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/21001372523405?sv=2026-02-06&spr=https&st=2026-10-30T00%3A38%3A33Z&se=2026-10-30T01%3A38%3A33Z&sr=c&sp=r&sig=kmUCWsPnubiMop0wzpelPhlZDaKqEmvMnqAZuUdOEok%3D)

> [!NOTE]
> **Note**
> 
> Record ID# is already marked as a unique key field by default.

> [!NOTE]
> **Note**
> 
> List – user fields cannot be marked as unique.
5. In the Properties tab under Basics, select **Must be unique**.
6. Save.

Now, when you set up the Quickbase Global Workflow action in FastField, you will be able to match these unique fields to your form fields, allowing their existing records to be updated.

## Set up in FastField

You'll then need to create a new Send to Quickbase Global Workflow action in FastField in order to map a form to your table and enable updates.

1. Go to **Workflow** > **Global Workflow** and select **+ New Workflow**.
2. Name this workflow and select **Send to Quickbase** as the action.
3. Name this action, choose or create an integration, and validate your Quickbase app ID.
4. Choose the Quickbase table that you would like to map the form data to.
5. Turn on the **Enable Updates** toggle. ![Enable Updates toggle in the FastField Quickbase integration](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/21001403479309?sv=2026-02-06&spr=https&st=2026-10-30T00%3A38%3A33Z&se=2026-10-30T01%3A38%3A33Z&sr=c&sp=r&sig=kmUCWsPnubiMop0wzpelPhlZDaKqEmvMnqAZuUdOEok%3D)
6. Choose your desired Quickbase [unique field](https://helpv2.quickbase.com/hc/en-us/articles/4570409950996-Requiring-unique-entries-in-fields-) and FastField form field, which will update the table's existing records when matched (instead of creating a new entry).

> [!NOTE]
> **Note**
> 
> Key fields must be marked as *unique* in Quickbase before they appear in the Quickbase Key Field drop-down (See *Set up in Quickbase*).
7. Complete the integration by mapping Quickbase table fields with form fields and save.