Quickbase January 2025 Release Notes

• • New
  • Enhancements
  • Beta opportunities
  • What’s fixed in Quickbase?
  • Feature retirements

New

Regex support in formulas

Quickbase now offers three regex (short for regular expression) functions in our formula language.

A regex is a pattern made up of symbols and characters. Regex is used to match strings with specific patterns, similar to a very powerful text search. Use these formulas to parse text so you can extract, replace, or match data in your table.

Learn more about Regex in formulas.

Wildcard searching

A new query operator, WC (Wildcard), is available in API calls and the report builder. It allows you to use an asterisk * or question mark ? as a wildcard character in search strings. This helps you search for relevant information, even if you're unsure of the exact spelling or further details.

• * finds any number of matching characters. For example, Jo* would match Joe, Jon, or John.
• ? finds a single matching character. For example, Jo? will match Joe or Jon, but not John.

Wildcard search is available in the following places:

• Quick search menu when using sidebar navigation
• Searching a new table report in the general search or column filters
• The search box on a dashboard when partial matches are allowed
• Report builder

To search for asterisks or question marks in your data, you will need to use \* or \?. If you don’t use a backslash, then the asterisks and question marks in your query will be interpreted as wildcard operators.

Audit logs added to Admin Console connected tables

By the end of January, we will add a new audit logs table to the Admin Console data source of connected tables (also known as Quickbase Sync).

This new table contains the following fields (similar to what is shown in the Admin Console audit logs page):

• Log ID
• First name
• Last name
• Email address
• Action
• Browser time
• IP
• User agent
• Session info
• Description
• Resource URL
• Application

The new audit logs table includes all schema-related, user management, and administrative events. User events (like logins and user activity) and record-level events are excluded. Refer to our Audit Log Library app to find out which specific actions are included in this new table.

Learn more about the logic of the new table and some of the limits in our help article.

Intacct connected tables—tracking and billing changes

As a reminder, Sage has announced a new requirement that incoming integrations to Intacct must provide a Sender ID. With this update, Sage is also changing the way they track account usage for integrations.

As a result, you may see a change in how much you are billed for Intacct. Connection owners, realm admins, and account admins will be contacted this month with instructions to update the affected connections.

Enhancements

Pipelines—date filter, new insight, FastField channel

Date filter

Available after January 14, we have a new Pipelines filter called is on a date. While setting up conditions and searches, you'll be able to filter on a precise date in any time zone.

My pipelines page insight—Updated at

With the introduction of service accounts, it's becoming easier to collaborate in Pipelines. To provide more visibility, we're adding a new column on the My pipelines page (labeled Updated at) that shows the last time a pipeline has been updated.

FastField channel

We've added the ability to prefill multiple subform instances in the Dispatch a Form step in the FastField channel.

The example below shows a form being dispatched with a subform that uses data from a Quickbase table. The number of subform instances dispatched will match the number of records in the table from step A.

This enhancement will be available by the end of January.

Report links—more flexible value matching

Builders can now directly control which query operator is used for report links, allowing flexibility in how records are matched.

Search easily for data in related tables

You’ve always had quick access to search for data across a table or app by using the magnifying glass at the top of the page. Now we’re improving that search to better help you find the data you’re looking for.

When searching on a single table, you can now check a box called Search related tables. When you do, any related parent or child tables will be searched as well.

Custom emails for personal reports

You can now select personal reports via the report widget in custom emails. When you create a new subscription for a personal email, this custom email will be set as a scheduled notification by default and the respective report will be included in the email body.

Dependency diagram—zoom and orientation controls

The dependency diagram helps you understand where data is coming from, for your formulas, lookups, and summary fields. Now it’s easier than ever to navigate the diagram when it is large and complex:

• Zoom control
• Ability to flip the orientation of the diagram

In case you missed it, in December we also released another update to this diagram.

Gauge charts—summary report formulas

You can use summary report formulas to perform calculations on a set of aggregate data by first summing the data set, and then calculating an average. We’ve now added them to gauge charts.

Note: Legacy gauge charts may not properly calculate if summary report formulas are used. Summary report formulas on gauge charts are not supported on legacy forms. They will be supported on dashboards in an upcoming release.

XML APIs—HTTP status code changes

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 aiming for a staged rollout over the next few months, starting in February with the following Quickbase error codes:

• 5 - Unimplemented operation
• 7 - API not allowed on this application table
• 9 - Invalid choice
• 10 - Invalid field type
• 12 - Invalid source DBID
• 14 - Missing DBID or DBID of wrong type
• 19 - Unauthorized IP address
• 23 - Feature not supported
• 27 - Registration required
• 37 - No such report
• 60 - Update conflict detected
• 70 - Account size limit exceeded
• 73 - Your account has been suspended
• 76 - Too many criteria
• 100 - Technical difficulties—try again later
• 102 - Invalid request—we cannot understand the URL you specified
• 110 - Invalid role
• 112 - No user in role
• 113 - User already in role

You could still benefit from the old behavior if you pass the optional header parameter X_QUICKBASE_RETURN_HTTP_ERROR=false.

Accessibility—ARIA landmarks

We’re committed to making Quickbase more accessible for all users. We've enhanced the accessibility of our platform by introducing ARIA (Accessible Rich Internet Applications) landmarks across various sections of our pages. These areas include the global bar and search, sidebar sections for apps and tables, table breadcrumbs, page actions, and more.

These improvements help assistive technologies navigate and interpret page structures more efficiently, making it easier and quicker for users to interact with different parts of the page.

RESTful API—estimated memory now available in getApp

The getApp API call helps you manage changes to your app by retrieving basic attributes such as date created and whether it’s open to everyone on the internet. The call will now also include an estimate of app’s size in memory, including dependent apps.

Improved platform performance

We’ve enhanced the platform’s capacity to handle workflows involving high activity. This improvement is designed to better support scenarios where multiple users are interacting with the same workflows simultaneously.

For example, this enhancement may improve the reliability of features like the Save & next option for forms, ensuring smoother navigation and expected behavior during periods of heavy use.

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
Pipelines OpenAI channel	We’re introducing the OpenAI channel to help you streamline workflows, automate text-based processes, and leverage AI capabilities directly within your apps. Learn more below	Available now for all to try

Pipelines OpenAI channel

We’re introducing the OpenAI channel to use in your Pipelines. This allows you to send prompts via the Chat Completion step and use the response from OpenAI in subsequent steps. Learn more about the OpenAI channel. 

This integration unlocks new possibilities for streamlining workflows, automating text-based processes, and leveraging AI capabilities directly within your applications.

The OpenAI channel will be available for all plans and enabled for everyone on December 17.

To connect, users need to provide their own OpenAI tokens.

This channel can be enabled and disabled as any other Pipelines channel (via Admin Console > Pipelines).

What's fixed in Quickbase?

Note: Pipelines bug fixes take effect on January 14. All other fixes take effect on January 12.

ISSUE	AREA AFFECTED	DESCRIPTION OF FIXED BUG
QBE020219	Pipelines	In the DocuSign channel, an error occurred for the Send an Envelope for Signatures using a Template step after clicking the Template field to select a template.
QBE020230	Pipelines	Adding or modifying a note to a running pipeline step caused the pipeline to turn off.
QBE020154	Pipelines	The link to Syntax help in the Text channel steps was not working.
QBE020232	Pipelines	An unnecessary number of popups were shown when reconnecting an account more than once.
QBE020233	Pipelines	There were unnecessary visible HTML tags in the channel descriptions.
QBE020234	Pipelines	Users using the sidebar navigation were shown the legacy navigation if they attempted to access Pipelines without the .ui subdomain.
QBE020242	Pipelines	In the HTTP channel, if Text (no parsing) is selected in the Make request step, in Expected payload type, attempts to parse the response will result in an Unknown format error.
QBE020242	Pipelines	The HTTP channel did not utilize the static IP configured for outbound connections.
QBE020254	Pipelines	In the HTTP channel, creating OAuth connections with empty scopes resulted in error.
QBE020004	Navigation	Clicking the table icon in the breadcrumbs did not direct users to the table’s default report.
QBE020155	Navigation	A tooltip placed at the horizontal edge of the page caused additional scrolling in some browsers.
QBE020196	Custom emails	Custom emails were incorrectly generating a login event in audit logs with an invalid session ID.
QBE020226	Custom emails	Formula URLs were displayed as links in the email output, as opposed to the link text.
QBE020153	Custom emails	A scheduled email that is not sent still updates Last Visited for the target recipient.
QBE020199	Performance optimizer	Some application instability occurred when optimizing a report that grouped deleted fields.
QBE014573	App and table management	The Custom data rules section in advanced settings was not properly displaying in Firefox.
QBE016221	App and table management	The Show in table bar option could not correctly be set in Firefox.

Feature retirements

End of Life

ToUser() formula function with only the numeric portion is unsupported

In the December release, we added support for the ToUser() formula function to operate on a user ID. This feature is intended to work on the complete user ID, including the letters (for example, 123456.abcd).

Some customers may have been using this previously without the letters, which was a bug. In the February release, formulas that only have the numeric portion of the User ID will stop working and customers will need to use the complete user ID. We are attempting to identify customers using this technique and proactively reach out, but may not be able to identify all scenarios.