Create a FastField form from a Quickbase table

Create FastField forms based on your Quickbase table schema. When someone submits a response to a form created this way, responses are automatically saved in Quickbase. 

How to create a FastField form from a Quickbase table

There are two ways to create a FastField form based on a Quickbase table:

• From Quickbase (through single sign-on linking)
• From FastField (through user token linking)

From Quickbase

Create a FastField form directly from your table in Quickbase. This requires you to first link your FastField and Quickbase accounts for single sign-on (SSO) from the Permissions page of the Quickbase Admin Console. Then:

1. In Quickbase, go to the table you want to use.
2. Open the table settings, and then select Forms.
3. Select New FastField form.
   This opens FastField in a new tab.
4. Enter a name for your form, and then select the fields you want to include.
5. Select Save and Edit.
   This saves your changes and creates the form. You can now make changes to the form layout and settings. After you're done, people can start submitting responses. 

From FastField

If your accounts are not linked for SSO, you can still create a FastField form based on a Quickbase table from the FastField Portal. This requires linking your accounts with a user token. To do this:

1. In the FastField Portal, select + New Form > Import from Quickbase.
2. Select an existing Quickbase integration or create a new one.
3. Choose a table, and then select Next.
   This selects the table to base the FastField form on.
4. Map the fields to include in the form. 
   To include a child table as a subform, select the table name and map the fields.
5. Save your changes.
   This opens the Form Builder, where you can continue editing your form.

Parent and child tables

When the table you select for the integration is a parent table, you can also connect child tables. They are automatically available when you're mapping fields. When you create a FastField form based on a Quickbase table, child tables are imported as subforms. 

Limitations

Submission failure notifications

If a FastField form submission fails to upload a new or updated record to a Quickbase table, no alert is sent to notify anyone of this failure. An Upsert Failure log displays in the Submissions activity log within FastField, however.

We are planning to add notifications for upsert failures in the future.

Field mappings

Currently, the following fields cannot be mapped with complete accuracy between Quickbase and FastField.

• Multi-choice fields that pull choices from another field or table are mapped as Text fields with no choices to select.
• Lookup fields cannot be mapped.
• User fields cannot be mapped.
• Attachment fields in Quickbase cannot be mapped to a Document Viewer field in FastField.
• Rating fields are not mapped to Quickbase when the N/A option is selected.