Quickbase February 2025 Release Notes

Release date
February 9, 2025

New

Quick Insights

Previously available as a beta feature, Quick Insights is now generally available. Use it to view predictive analytics powered by Data Analyzer directly in your apps. To generate insights:

Open the column menu of any checkbox, text, or multi-select field in a table report.
Select the Quick Insights option.
Select the outcome you’d like to predict, and Data Analyzer will generate insights that include the correlating factors.

Pipelines OpenAI Channel

Previously available as a beta feature, the OpenAI channel will be generally available on February 18. This channel allows you to connect to the Chat Completion API endpoint of OpenAI with your own credentials and send a custom prompt.

Learn more in our blog post or help article.

Enhancements

Pipelines—quick start feature

We are improving the speed, reliability, and consistency of certain triggered pipelines with new quick start functionality. Pipelines eligible for quick start will start running up to 300% faster and typically:

Have up to three steps (the trigger and two actions).
Are driven by a human in a Quickbase workflow, triggering a few times per minute.
Operate on a low volume of data (less than 100KB).

As announced in December 2024, this new capability is now fully rolled out and available to all our users to enjoy faster trigger times. To see which of your pipelines is using quick start, check the activity log and look for the lightning bolt icon. The lightning bolt icon will begin appearing after February 18.

Pipelines—improved support for field mapping suggestions

When configuring steps in a pipeline, you can use the Suggestions tab to get AI suggestions for field mappings. Available February 18, AI suggestions now include even more field types, as well as the reasoning behind each suggestion.

Note: The quality of suggestions is highly dependent on the details of your pipeline and steps, especially the pipeline’s name, its description, the step names, and notes. For optimal results, it’s best to use field mapping suggestions on pipelines created with our AI Smart Builder.

Pipelines—sorting and pagination in Connection Central

App builders can use Connection Central to understand how data in your app is integrated with other apps and other systems outside of Quickbase. We're continuously enhancing this capability with new functionality. By the end of February, you will be able to sort by field, type, and table.

You’ll also be able to review connections more efficiently with pagination in the side panel.

Pipelines—caution message for stopping a pipeline’s instances

Each time one of your pipelines runs, those are separate instances. We’ve added a tooltip to indicate that turning off a pipeline that is currently running will also stop all running instances. This will begin appearing on February 18.

For example, if you are the pipeline builder and two of your users trigger the same pipeline, that means that two instances of that pipeline are running. If you disable that pipeline while both instances are still running, those instances will stop instead of completing.

A screenshot of the tooltip that reads: Turn off and stop all instances

Sidebar navigation—skip link support

In the sidebar navigation, we'll be introducing skip link support to more easily allow users to skip to different sections of the page. This was built for people who use assistive technologies.

Learn more about Quickbase's approach to accessibility.

Formula checker styling updates

The formula checker lets you review the result and runtime of each expression in a formula. We’ve updated its styling to make it even easier to use. Just enter a record and field ID, and select Run to review its expressions. Learn more in our help article.

Charts—customize min./max. Y-axis values

Users customizing a report can now set minimum and maximum Y-axis values for both the primary and secondary Y axis. This allows for deeper customization of line and bar charts.

Note: Setting these will remove Quickbase’s default axis calculation. Y-axis overrides will not take effect in legacy charts.

Screenshot of the Y axis settings menu

Example of a bar graph with the Y axis set at a minimum value of 500,000

In this example, the Y axis begins at $500,000.

Feedback links now redirect properly

Your feedback is crucial for helping determine the future of the Quickbase platform. Use the Give feedback button, located in the help menu, to send your feedback or vote on ideas submitted by others.

Previously, direct links to individual feedback entries would redirect you to a non-functional login page. Now, you’ll be taken directly to the feedback entry if you’re already logged in. If not, you’ll be prompted to enter your realm before logging in to view the entry.

Learn more about how we use your feedback.

Signing in from the Quickbase company website

If you are on our company website (www.quickbase.com) and use the Sign In link, Quickbase will now detect if a session exists with a realm and direct you to that realm. If not, you’ll be able to enter one.

File management page—UI and capacity improvements

The file management page lets you view file attachments across all tables of an app. We've updated this page to be more consistent with the appearance of other app builder pages. We also optimized the file management page to support apps with more files (100,000+).

Last visited date now available for user groups

As an app builder, you can go to the Users page to see the date each individual last visited an app. Previously, this only applied to users added to an app individually. Now, admins can also view the last visited date of users who have access only via their membership in user groups. This change is reflected in all areas of the product where Last visited is exposed.

XML APIs—HTTP status code changes (wave 1)

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 this month 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 can still benefit from the old behavior if you pass the optional header parameter X_QUICKBASE_RETURN_HTTP_ERROR=false.

Audit logs styling

The styling and design of the audit logs feature available in the admin console has been updated to enhance the user experience.

Screenshot of the audit logs feature in the admin console

Gantt and Data Analyzer plugins—Exchange and app copy support

Users can now obtain applications from the Exchange with plugins pre-installed in them. In this release we will enhance the Gantt and Data Analyzer exchange applications. Users who get the Exchange template apps following this release will no longer need to install the plugin.

Plugin configurations will be kept when apps are copyied or sandboxed. Users can then use the plugins in these environments without needing to adjust the plugin configuration.

Intacct connected tables—tracking and billing changes

As a reminder, to continue using Intacct connected tables, your existing connection needs to be updated to use your company's own Sender ID. This is necessary to align with Sage’s standards that require integrations to authenticate using the customer's own Sender ID. Customers will need to review their active Intacct connections and update each Intacct Sync connection in Quickbase to provide their company’s Intacct Sender ID before February 28th, 2025.

Affected customers may need to contact whoever manages their Intacct instance within their company to find their Sender ID. If the company doesn’t seem to have a Sender ID, it may be because they have not purchased a Web Services Developer License from Intacct. In that case, they will need to reach out to their account manager at Intacct. Depending on the volume of the Intacct API usage, customers may also need to upgrade the service level tier for their developer license.

As a result, customers may see a change in how much they are billed for Intacct. Connection owners, realm admins, and account admins have been contacted with instructions to update the affected connections.

Platform performance

Initial load time across all pages in Quickbase has been improved.

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

What's fixed in Quickbase?

Note: Pipelines bug fixes are deployed on February 11. All other fixes are deployed on February 9.

ISSUE	AREA AFFECTED	DESCRIPTION OF FIXED BUG
QBE019773	Pipelines	After selecting View run activity, the date/time filter did not clear (if applied) and the run was partially displayed.
QBE020288	Pipelines	When searching for pipelines steps, Quickbase steps did not appear first in the list of results.
QBE020263	Pipelines	In the SharePoint channel, the Move the file step resulted in error when the Drive field was filled in. Note: This step does not support moving between drives and the Drive option of the step should be filled in only with the current drive the pipeline is using, or left blank.
QBE020270	Pipelines	The Channels page could not be accessed without prior login to Quickbase.
QBE020236	Pipelines	Links in the top navigation in Pipelines did not have the option to open in a new tab (via right click > Open Link in New Tab or Ctrl + click).
QBE020172	Navigation	Personal reports in sidebar navigation reports panel were not contained in the drop-down menu and were not scrollable.
QBE020197	Navigation	When using the sidebar navigation, the legacy report table header and data were misaligned when sorting and scrolling through the report.
QBE019969	Navigation	When using the sidebar navigation with new style table reports, items in the Reports drop-down menu are unclickable unless you click directly on the text.
QBE020116	Navigation	When using the sidebar navigation, the first column in legacy table reports was no longer sticking.
QBE020214	Navigation	URL fields containing certain malformed links were causing table reports to fail to load.
QBE020006	Forms	Field-level help text (found in a field's settings) in the new forms version wasn't rendering line breaks correctly, showing HTML tags instead.
QBE020052	Forms	Hyperlinks in rich text fields with logging enabled weren't clickable in view and edit mode in the new forms version.
QBE013330	Visual builder	Fields were incorrectly created with duplicate field names and allowed duplicate names to be set.
QBE020019	Mobile	Nav 2.0 formatted links in the Quickbase mobile app redirected some users to the wrong page. This issue will be resolved in version 1.67 (to be released by Feb. 12).
QBE020166	Mobile	Formula – rich text buttons in the iOS Quickbase mobile app navigated to an error page. This issue will be resolved in version 1.67 (to be released by February 12).
QBE020295	Billing	Previously, any email domain could be added to an app, even if it wasn’t registered with a company in Quickbase, potentially increasing paid user counts. Now, users from unregistered domains will not be counted as paid seats until they have registered and gained app access. This update ensures more accurate user billing while maintaining flexibility in domain-based access.
QBE020287	App management	The file management page performed poorly on tables with more than 100,000 files.
QBE016454	App management	The list of files could not be exported from the file management page in certain browsers.
QBE020309	App management	On the Manage Users page, the number of users for email domain groups not registered to a company belonging to the realm was shown, instead of being hidden.
QBE019990	ALM sandbox	Some application and table ID placeholders remained in sandbox change logs and in the live application.
QBE020026	ALM sandbox	In a sandbox, if a scalar field's type was changed to a lookup type, it may not have been recognized for publishing and, therefore, failed to be published. Other properties of the field were noted as being changed, but the field type change was ignored.
QBE020249	Search and reports	`{{Not wildcard match}}` was not reliably returning results.
QBE020300	Connected tables	Dropbox connections for connected tables were failing.
QBE020283	Document creation	Requesting document templates using any Make request step in Pipelines failed when a realm leveraged IP filtering policies.
QBE020235	Document creation	Text Multi-Line field references containing a `/` after a page break entered on legacy forms corrupted .docx files.
QBE019840	Email subscriptions and reminders	Communication regarding send limits for subscriptions and reminders in documentation and warning messages was incorrect or unclear.
QBE020251	Custom emails	Including a field marker in the subject of a custom email notification caused changed fields on an included form to not show in red.
QBE018660	Account permissions	Duplicate email notices were sent when users without "create" permissions submitted a request to create an app.
QBE018358	`API_ImportFromCSV` and UI imports	Certain built-in fields, like `{{date created}}`, could incorrectly be updated via `API_ImportFromCSV` and UI imports.
QBE017817	Table reports	Newly created report links and `{{Add...}}` buttons on the parent side of a relationship did not respect the choice to not make it a default column.

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 this 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 have proactively reached out to customers we were able to identify using this pattern but may not be able to identify all scenarios.