Quickbase March 2025 Release Notes

Prev Next

Release date

March 16, 2025

New

AI-powered product help

Starting March 31, tapping into Quickbase's help resources is easier than ever. We’re introducing AI-powered Quickbase help, designed to give you support wherever you are in the platform.

Getting AI-powered help is simple to use. Select Ask Quickbase AI in the help menu and ask a question about the platform or task you want to complete in your own words.

Another way to access AI-powered help is by using the Get help skill when you open Quickbase AI from the global bar. This provides you with immediate answers and resources, right where you’re working.

With Quickbase AI-powered help, you can get on-demand help with platform topics and with AI responses that remember the context of your queries. By pulling resources from the Quickbase help center and integrating insights from user feedback, Quickbase AI help ensures that your AI responses are not only accurate, but also highly relevant to your specific needs.

Learn more about this new feature in our updated help article.

Audit logs access from any app

We're opening our audit logs to more roles. App administrators and super users can now access audit logs by going to App settings > App management. There you can view and filter audit logs specific to the current app.

This new page has additional filters for greater flexibility and to make the search process faster and more accurate. You can narrow down results to a specific table, resource type (field, record, etc.), or resource ID.

Learn more in our help article.

Screen shot of a audit log for an app in the App settings menu

Solution APIs and QBL—support for additional schema objects

We will release three new QBL (Quickbase language) versions:

  • V0.7 will be the default version. It supports forms (both legacy and new), dashboards, and cross-app relationships, in addition to all previously supported features. It will be generally available to everyone on March 31.

  • V0.8 supports connected tables. It will be available in closed beta on April 4. Sign up in the beta registration app to try it out.

  • V0.9 supports pipelines. It will be available in open beta for everyone to try on April 4.

Learn more about QBL and Solution APIs.

Pipelines—use AI to fill in steps

Starting March 25, pipeline builders can use AI to fill in all the fields in a pipeline step with a single click.

Smart Builder uses pipeline details (schema, name, and description) and step details (type, name, and notes) to populate all mandatory and some optional fields in your step. For this to work, make sure you have a valid connection selected first.

Pipelines—new activity events in audit logs

With the addition of service accounts, it’s become easier to collaborate in Pipelines. To provide more visibility, beginning on March 25, you will start seeing the following audit logs events related to pipeline operations:

  • Pipeline created

  • Pipeline updated

  • Pipeline deleted

  • Pipeline activated

  • Pipeline deactivated

  • Prompt sent to Pipelines Smart Builder

The new events will be available in the audit logs Admin Console connected (ACC) table.

Email domain group operations—new activity events in audit logs

We've added new audit logs for the following email domain group operations:

  • Add any email domain group to an app

  • Change the role assigned to an email domain

  • Remove an email domain from an app

The new events will be available in the audit logs Admin Console connected (ACC) table. View our full library of audit logs.

Enhancements

My apps page—more visibility

In the coming weeks, we’ll be rolling out improvements to the My apps page. Our goal is to reduce the likelihood of apps falling off the page for users with a large number of apps. We’ll continue to release more improvements over the coming months. 

Audit logs Admin Console connected (ACC) table—new fields

We offer a series of special connected tables that pull administrative data from your account’s admin console (users, apps, audit logs, etc.). For better traceability and transparency, we're adding two new fields to the audit logs ACC table: User ID and Payload changes. These fields will be available by the end of March.

Performance analyzer

The performance analyzer will now show the number of operations detected in any part of a trace.

Dashboard gauge charts—summary report formulas

In January, we added summary report formulas to standalone gauge charts. This lets you perform calculations on a set of aggregate data by first summing the data set, and then calculating an average. Now, summary report formulas are supported on all gauge charts, whether they're embedded on a dashboard or not.

Single sign-on (SSO) prompt

We’ve improved the sign-in prompt to increase clarity. Previously, users were asked if they had a corporate username and password to sign in with. Now, users are asked specifically if they have an SSO account.

Also, new users registering with a Quickbase username and password in a realm with SSO will not be asked if they have corporate SSO credentials. This will help reduce confusion and error.

FastField location fields now map to Quickbase address fields

Users of the FastField integration can now map FastField Location/GPS fields to Quickbase Address fields.

Previously, the latitude and longitude coordinates captured from the Location/GPS field on a FastField form did not directly transfer to the Address field on a Quickbase table. This has now been improved to further improve your field-to-office workflow.

Learn more about connecting FastField forms with Quickbase tables.

Pipelines FastField channel—pre-populate photos and documents

You can now dispatch a FastField form with pre-filled photos or documents using the Pipelines FastField channel.

To do this, select a Single Photo or Document Viewer field to pre-populate. Then, the File Transfer Handler allows you to retrieve a file from a Quickbase record or any other file transfer step within the pipeline.

This FastField enhancement will be available by the end of March.

Pipelines—new search option for power builders

On March 25, we’re adding a new way to search in pipeline steps. Typing / will open a filter search, which will be replaced by the selected field, including any spaces.

Pipelines planned maintenance on March 25—refresh may be needed

We are doing planned maintenance of Pipelines on March 25 before 8 AM EST. During the day, if you are working on Pipelines and the UI does not respond properly or responds with an error, please refresh the page to fix it.

XML APIs—HTTP status code changes (wave 2)

By default, our XML APIs return an HTTP status code of 200, even if there’s an error. To partially overcome this, we previously introduced an optional header parameter that causes Quickbase to return a 400 (bad request) HTTP status code in case of an error.

Now we are further evolving our XML APIs so that they can return proper HTTP status codes based on the Quickbase error codes, even without supplying the optional header parameter. We are doing this to harmonize our APIs with the latest industry standards.

We are doing a staged rollout. We started last month with the initial wave 1 of error codes. This month, the following Quickbase error codes will be impacted:

  • 1 - Unknown error

  • 2 - Invalid input

  • 4 - Bad ticket

  • 6 - Syntax error

  • 8 - SSL required for this application table

  • 11 - Could not parse XML input

  • 13 - Invalid account ID

  • 15 - Invalid hostname

  • 20 - Unknown username/password

  • 22 - Sign-in required

  • 24 - Invalid application token

  • 25 - Duplicate application token

  • 26 - Max count 

  • 28 - Managed by LDAP

  • 29 - User on Deny list

  • 31 - No such field

  • 33 - No such query

  • 34 - You cannot change the value of this field

  • 35 - No data returned

  • 36 - Cloning error

  • 38 - Periodic report contains a restricted field

  • 52 - Duplicate field

  • 53 - The following required fields are missing from your import data:  [[]...]

  • 54 - Cached list of records not found 

  • 61 - Schema is locked

  • 74 - You are not allowed to create applications

  • 75 - View too large

  • 77 - API request limit exceeded

  • 78 - Data limit exceeded

  • 80 - Overflow

  • 81 - Item not found

  • 82 - Operation took too long

  • 84 - Database error

  • 85 - Schema update error

  • 87 - Invalid group

  • 101 - Quickbase is temporarily unavailable due to technical difficulties

  • 103 - The Quickbase URL you specified contained an invalid srvr parameter

  • 104 - Your Quickbase app is experiencing unusually heavy traffic. Please wait a few minutes and re-try this command.

  • 105 - Quickbase is experiencing technical difficulties

  • 111 - User exists

  • 114 - Must be admin user

  • 150 - Upgrade plan

  • 151 - Expired plan

  • 152 - App suspended

Beta opportunities

Here are some new features for you to try out while we're still developing them.

FEATURE

DESCRIPTION

HOW TO PARTICIPATE

New forms on Quickbase mobile

Mobile users can use the new forms experience to add, view, and edit records while on the go.

Join the waitlist in the Beta Registration App

Create FastField data tables from Quickbase reports

You can now use Quickbase reports as the source of FastField data tables.

Learn more below

Available for all FastField accounts to try now in the FastField Portal

Create Quickbase tables from FastField forms

Build a form in FastField and use it to create a new table in Quickbase—instantly!

Learn more below

Available for all FastField accounts to try now in the FastField Portal

Create FastField data tables from Quickbase reports

Data tables are a way to sync your Quickbase data with dropdown lists used in FastField forms for real-time updates. Previously, data tables could only be synced with Quickbase tables. Now, you can use Quickbase reports as the source of a FastField data table. By using a Quickbase report, your data table’s values are automatically filtered according to the filters you have set up in your report.

Create Quickbase tables from FastField forms

FastField lets you create mobile forms in seconds—straight from your Quickbase table or by using the AI Form Converter. Now, you can also instantly create a new Quickbase table from a form you’ve made in FastField.

This is helpful if you want to start by making a form in FastField, and have it automatically create a new table in Quickbase to store its data in. To do this:

  1. Build a form in FastField (with AI or from scratch)

  2. In the Form Builder, go to Advanced Options > Connect to Quickbase Table

  3. Choose your integration and app, and select Add new for the table

Note: This feature requires you to set up a Quickbase user token integration in FastField.

What's fixed in Quickbase?

Note: Pipelines bug fixes are deployed on March 25. All other fixes are deployed on March 16.

ISSUE

AREA AFFECTED

DESCRIPTION OF FIXED BUG

QBE020010 

 

Pipelines 

Better support for callable pipelines through versioning and rollback. 

QBE020372 

Pipelines 

In the Quickbase channel, adding a large number of fields in the Update a record step resulted in error. 

QBE020378 

Pipelines 

In the ServiceNow channel, an error occurred when loading tables for step inputs. 

QBE020400 

Pipelines 

In the Mailchimp channel Search Email Events step, an error occurred when attempting to select a campaign. 

QBE020409 

Pipelines 

Improved messaging when user is switching between normal and service accounts in different browser tabs while building pipelines. 
 
There were issues when users switched between normal and service accounts in different browser tabs while building pipelines. 

QBE019899 

Pipelines 

In the new version of Pipelines Designer, the Fields for Subsequent Steps search and dropdown selection function mishandled field names that contained spaces. 

QBE020373 

Pipelines 

An error occurred when trying to set a value for a Rating field. 

QBE020374 

Pipelines 

In the Activity tab, the indicator for running pipelines was not aligned with the indicators for finished runs. 

QBE020375 

Pipelines 

In Pipelines Designer, the ? button above the controls still displayed even though it has no function anymore. 

QBE020376 

Pipelines 

On the My pipelines page dashboard, long pipeline names could not be viewed in full. Now, the full name is shown in a tooltip. 

QBE020377 

Pipelines 

When deleting a pipeline from the My pipelines dashboard, the confirmation message did not display the pipeline name. 

QBE020421 

Pipelines 

The My pipelines page did not accurately reflect the exact trigger date/time. 

QBE018118

Pipelines

Currently, the Microsoft Graph API does not support creating or updating SharePoint List Items that contain Hyperlink fields.

As a workaround, use a Text field instead of a Hyperlink column. Then, format the Text field to display as a clickable hyperlink in SharePoint.

For instructions, refer to this SharePoint tutorial.

QBE020421

Pipelines

The last triggered date showed different date/time than in the activity log.

QBE020448

Pipelines

When working on especially large data sets, the Import from CSV step in the Quickbase channel was intermittently failing to properly transfer all records.

QBE020433

Pipelines

When connecting to the Box channel, a pop-up prompted users for their username and password and then closed before they could grant Pipelines access to their data.

QBE020454

Pipelines

There was a broken connection in the Marketo channel.

QBE020498

Pipelines

Work on a current performance improvement caused a few pipelines to not trigger as expected.

QBE014174 

Mobile 

Multiple-choice fields configured to be displayed as radio buttons in legacy forms on mobile and required by a dynamic form rule were still displaying the None of the Above option. 

QBE019938 

Forms 

Images inserted into a Rich text field that had log edits enabled did not appear. 

QBE018952 

Forms 

Some valid multi-select lookup values incorrectly showed an Item has been removed tooltip on hover. 

QBE020324 

Audit logs 

Activate/deactivate user token activities from the Admin Console were not respected in the audit trail. 

QBE020419 

Audit logs 

In certain workflows, a subset of new style reports did not correctly show in audit logs. 

QBE020422 

Audit logs 

Email addresses with a + sign could not be searched in audit logs. 

QBE020422 

Audit logs 

Email addresses were case sensitive when searching audit logs. 

QBE020323 

Audit logs 

Certain audit events for super user assign/unassign activities were missing in the audit trail. 

QBE020325 

User management 

REST API deny/undeny user activities were not respected in the audit trail. 

QBE020389 

Login 

At the single sign-on (SSO) prompt, users’ selection did not save in the browser when selecting {{no}}. We’ve also improved the behavior so that users registering for a realm that has SSO enabled no longer need to make this choice on their first time signing in. 

QBE020410 

 

Custom emails 

 

Custom emails or record change events with large amounts of information (like embedded images in rich text fields) sometimes did not reliably send or get stored in audit logs. 

QBE020407 
QBE020411 

Document creation 

In some cases, realm-level IP filtering was unreliable with document creation and custom emails. 

QBE020010 

Solutions versioning 

On the Solutions page, the restore date was incorrect, causing an error. 

QBE020329 

Connected tables 

We made improvements to Admin Console Access connected tables to reduce the likelihood of timeouts caused by apps with large groups. 

QBE020316 

 

Connected tables 

Connected table text filters using one of the following operators returned unexpected results: comes before, comes before or same as, comes after, comes after or same as

QBE020364 

Connected tables  

Google Drive connected tables used a CSV file's creation date to determine which file was the oldest or newest in a folder. Now, we use the time the file was placed in the folder so that it matches the behavior of other CSV connected services (Box, Dropbox, SFTP). 

QBE020379 

Connected tables  

When an app is not assigned to a user token, the error message shown did not state the problem clearly. It now states: User token is invalid

QBE020086

New Forms 

URLs and Emails were not recognized as links in text and multiline-text fields.

QBE020326 

New Forms 

In edit mode, URL links added to rich text fields opened directly when clicked (instead of showing the popup screen to edit or unlink). 

QBE020394 

Service accounts 

When attempting to switch to a service account, error details were not displayed if there was one. 

QBE020390 

File attachments 

Trying to select a large amount of files to delete from the file management page would result in an error. Now, up to 1000 files can be deleted. 

QBE020381 

API 

Using the performance profiler on {{API_ImportFromCSV}} did not provide a breakdown of where time was spent.

QBE020355 

REST API 

When copying Python, the copy code logic in the developer portal did not accurately reflect what was shown on the screen.

Feature retirements

Audit logs Admin Console connected (ACC) table notification_sent action

We removed the notification_sent action from the audit ACC table. For a full list of supported actions, visit our Audit Log Library app.

Automations, Application Webhooks UI, and Quickbase Actions retirement timeline

After careful consideration of your valuable feedback, we're pleased to announce a more customer-friendly approach.

After August 31, 2025, existing customers will no longer be able to create new Actions. This is the only change we'll implement this year, aligning Actions with the current state of Automations. There are no changes scheduled for Webhooks or Automations at this time.

As a reminder, Automations are currently unsupported, and we recommend migrating to the more powerful and flexible Pipelines capability. It’s no longer possible to create new Automations.

Actions, and the Application Webhooks UI, are not available on newly-created accounts. Existing Automations and Actions, however, will continue to run indefinitely and you’ll still be able to enable or disable them as needed.

Learn more in our blog post.