April 13, 2025
New
Updated forms experience on Quickbase Mobile
On April 21, our updated forms experience (previously only available on desktop) will become generally available in the Quickbase mobile app (version 1.68) and any mobile browser.
Designed for business users on the go, this update makes it easier to view, edit, and add records from your mobile phone or tablet. With a modern layout, streamlined workflows, and enhanced functionality, you can stay productive from anywhere.
Depending on your form settings, your end users may experience a change on April 21.
- Automatic update: If you’ve assigned the updated form version for Add, Edit, or View mode on desktop and set mobile to Use full site forms, then starting April 21, your mobile users will automatically see the new form on their devices—no extra setup needed.
- No change: If you’ve assigned a legacy form specifically for mobile, it will not automatically update—your mobile users will continue to see the legacy form.
Learn more about the updated mobile form experience or how to assign forms for mobile.
Role property to restrict table access
A new setting is available for each role that will restrict new tables from being available to that role. This gives you more control over who can access new tables by default.
Audit logs—restore changed data
Realm admins and app admins can now restore changed and deleted data from data change logs.
Data change logs have been available for years, but once enabled for a particular app, app admins also had to enable tracking on a field-by-field basis. Now, once data change logs are enabled for an app from the admin console, we'll automatically start logging data changes for all data-entry (scalar) fields fields where data has been modified. Unlike the existing behavior, we'll only show fields that have been modified in the data change logs. Learn more about enabling data change logs.
Additionally, admins with access to app and realm audit logs can restore modified data directly from the audit logs page by selecting the fields that they want to restore. This does not require the assistance of our Tech Support team. Learn more about restoring data.
Show specific fields in data change logs
With this release, we’re also changing the fields we show in data change logs. Previously, we showed all fields that had the Track field option enabled. Now, we'll only show fields that have been modified. If you need a certain field to always be present, whether it’s actually changed or not, admins can check the Show in data changes checkbox under Advanced field settings. This setting was formerly Track field.
For any existing apps where data change logs have already been enabled, we'll automatically start auditing all scalar fields. If the former Track field option (now Show in data changes) had already been enabled, those fields will now always show in the data change logs (even if data hasn’t been changed). This can always be changed from the field properties page.
Note: The current limit of 50 auditable apps per realm still applies.
Median functions
You can calculate averages in many places in Quickbase, like with the Average()
formula function. This gives you the arithmetic mean. We are now giving you more flexibility in how you calculate averages, by adding the ability to calculate median values in the following places:
- Summary reports: aggregate by
- Summary fields: summary function
-
Formula fields:
Median()
When calculating on fewer than 1,000 data points, an exact algorithm is used. With greater than 1,000 data points, an estimated algorithm is used.
Join formula
We’ve added a new Join()
formula function to append a set of field values by a delimiter (like a ,
or -
) you define. This can be used to combine fields on a table or with a formula query.
For example:
var Text query = "{3.GT.'" & "0" & "'}";
var RecordList recs = GetRecords($query, [_DBID_B]);
var TextList vals = GetFieldValues($recs, 7);
Join($vals,"-")
Export data-entry fields
A new option is available on the Import/Export page of a table to allow exporting only data-entry (scalar) fields. This allows for easy data backup or transfer without manually selecting fields on a report. Learn more about exporting data out of Quickbase.
Enhancements
Increased export limits
Exports from the Import/Export page are now zipped during transport, allowing for exporting larger datasets. A table can have a maximum underlying size of 500 MB. The compressed file being exported must be under 150 MB.
Create 10 lookup fields at once
Previously, app builders could add up to three lookup fields to a relationship at a time. We have increased this limit, enabling you to add up to 10 lookup fields at one time.
RESTful APIs—delete records by record ID#
The deleteRecords endpoint now accepts an array of up to 50,000 record IDs. This provides a more efficient way to delete records.
Audit logs—more events and details
We've been continuously improving the level of detail and coverage in audit logs by adding more events, resource URLs, and more detailed and consistent descriptions. The resource URLs have also been updated to match our new navigation format for consistency.
Check our recently released Audit Logs Library app for more information about all tracked events.
Document Creation—inline style control
To improve formatting consistency in documents with rich text fields, the source styling for these fields will change from block to inline. This will reduce situations where extra wrapping or line breaks may occur. Builders can revert to the previous behavior by changing inline=”false”
to rich text field properties in the source code.
Pipelines—usability
Based on your feedback, we made multiple usability improvements in Pipelines. You now have the ability to:
- Collapse all steps of a pipeline in the designer canvas
- Refresh schema for a single step
- Expand more than one section in a step
- View long pipeline names in a tooltip on the My Pipelines page
We’ve also made the following improvements:
- Added table information for Quickbase target fields
- Added а Go to step action when you have chosen a target that redirects you to the target step in the designer
- Widened the pipeline name input to take up all available space when editing
- Added a dedicated Generate steps (with AI) button
- Added three separate buttons for Create pipeline, Generate with AI and Import on the My Pipelines page (applicable for larger screen sizes)
- Prevented zoom outside of the designer canvas
- Improved search results when adding steps in a pipeline
Pipelines—credentials handling
By the end of April, the credentials handling for the following Pipelines steps will be improved:
- Webhooks channel - Make request
- Quickbase channel - Make request
- CSV Handler channel - Fetch CSV
- JSON Handler channel - Fetch JSON
All sensitive fields (like passwords and tokens) will be masked with asterisks (*) when building or editing a pipeline. The same approach will be applied to the activity log (where those values are present). In the YAML export those values will be completely removed.
Performance improvements
We’re continuously improving the performance of the Quickbase platform. We’ve made significant improvements to the following areas:
- Adding lookup fields to tables with large amounts of records
- Calculating work date fields (to accommodate durations that include partial days)
- Apps being read into memory that often delete large amounts of records will now read faster
- User and List-User field dropdowns on new forms
XML APIs—HTTP status code changes (wave 3)
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 with the initial wave 1 and wave 2 of error codes. This month, the following Quickbase error codes will be impacted:
- 21 - Unknown user
- 30 - No such record
- 32 - The application does not exist or was deleted
- 50 - Missing required field
- 71 - Database size limit exceeded
- 83 - Access denied
Upcoming change for QuickBooks connections for connected tables
Later this year, Intuit is ending support for minor versions 1-74 of their Accounting API for QuickBooks Online. In anticipation of this event, QuickBooks connections for connected tables in Quickbase will begin using minor version 75 of that API on April 16. We don’t anticipate issues, but please reach out to Quickbase Technical Support if you encounter problems with your QuickBooks connection after this change.
Beta opportunities
Here are some new features for you to try out while we're still developing them.
FEATURE | DESCRIPTION | HOW TO PARTICIPATE |
Connected tables—QBL v0.8 | Test and explore this new QBL (Quickbase language) version that supports connected tables with Quickbase sources. Learn more about what’s supported. | Join the waitlist in the Beta Registration App |
Pipelines—QBL v0.9 | Use this new QBL (Quickbase language) version to import or export pipelines that use specific channels. Learn more about what’s supported. | Available now—specify 0.9 as the QBL version when making requests with the Solution APIs |
Enhanced OpenAI and Bluebeam Pipelines channels | Try out the new Enhanced OpenAI and Bluebeam channels.
|
Join the waitlist in the Beta Registration App |
Aggregate functions on formula queries | Use aggregate functions like Min, Max, Avg, Median on the results of a formula query:
|
Available to try now |
AI App Intelligence
Coming this month, AI App Intelligence will be available in beta to provide admins with AI-generated app summaries. Accidental admins (people who unexpectedly inherit apps) often struggle to understand the structure and purpose of unfamiliar apps. This feature provides instant clarity by summarizing an app’s value, structure, and key information without the need to click through every table or record.
AI App Intelligence comes with the following capacities:
- One-click app overview: Get a structured summary that outlines the app’s goals, features, tables, and data relationships.
- Smart guidance for new admins: Understand app functionality instantly—no need to explore each page manually.
- Easy onboarding: New admins can hit the ground running with confidence.
- In-context access: Admins never have to leave the page to get oriented.
This feature also includes the following details:
- An executive summary
- Key app features
- Roles and responsibilities
- Table relationships and data flows
- Frequently referenced fields
How to try it
AI App Intelligence will be available in beta to Business and Enterprise plans by the end of this month. To access it, go to App Settings > App Management > Show app info > Show app summary. No configuration is needed to start using it, but you must have Generative AI enabled in your realm.
What's fixed in Quickbase?
Pipelines bug fixes are deployed on April 15. All other fixes are deployed on April 13.
ISSUE | AREA AFFECTED | DESCRIPTION OF FIXED BUG |
QBE020471 |
Pipelines |
Scrolling did not work for update steps when there were multiple targets. |
QBE020472 |
Pipelines |
The AI button to fill in step fields appeared unnecessarily for steps without fields. |
QBE020475 |
Pipelines |
While updating a Pipeline using the Solution APIs, a notification appeared if the pipeline was not currently editable. |
QBE020460 |
Pipelines |
When attempting to connect a Docusign developer account with Pipelines, an error message occurred after entering your password in the Docusign popup. |
QBE020462 |
Audit logs |
Record_edit audit events did not contain a hyperlink to the respective record. |
QBE020467 |
Webhooks |
Applications with many users (50,000+) sometimes experienced performance issues loading the webhook edit page. |
QBE020434 |
Connected tables |
Some Quickbase staff had an access status of paid seat in the Admin Console connected users table. |
QBE020447 |
Connected tables |
Some connected table refreshes resulted in timeout errors, which have now been reduced. |
QBE020086 |
Forms |
URLs and emails were not recognized as links in text and multiline text fields. |
QBE018167 |
Mobile |
Formula Rich-Text fields containing images were not displayed correctly on mobile dashboards. This issue will be resolved in version 1.68 (to be released by April 21) |
QBE020466 |
Audit logs |
In certain cases, app admins could not access audit logs in an application when IP filtering was enabled. |
QBE019564 |
Forms
|
The default value was not shown in the List User field with successive record creation. |
QBE020461 |
Forms |
Filters on report formulas were not being respected when drilling down from KPI/gauge widgets. |