Skip to main content

QBL version 0.11 overview

Beta

This is a beta feature, which means we’re still developing it. Some functionality might change.

Release date: July 21, 2025

This article documents the changes made in QBL v0.11, the objects this version supports, and unsupported elements.

Change log

This release includes support for homepages, rich text pages, and code pages.

Note: Quickbase automatically updates table and app ID links within the same app to reflect the new IDs generated during QBL create or update actions in homepages, rich text pages, and code pages. Links that point to resources outside the app (including within the same solution) or to other types of resources are not updated.

Supported objects

These objects are supported in QBL v0.11:

Unsupported elements

The following table shows supported schema and any exceptions or unsupported elements.
Unsupported elements are not included when a solution is exported.

Supported schema Unsupported
Apps

Temporarily unsupported:

  • Apps with connected tables cannot be updated. This limitation will be removed soon.

Unsupported app settings:

  • Allow users who are not administrators to make a Quickbase Sync connection to this app
  • Only approved users may access this application
  • Only users logging in from approved IP addresses may access this application
  • Load all embedded reports on a form when the form loads
  • Private apps
Fields and formula fields

Unsupported fields:

  • vCard fields
  • iCalendar fields

These fields are exported with the Unsupported type in QBL. 

They cannot be created or updated by the QBL. To update or create these fields, do so manually in the Quickbase platform.

Formulas that refer to these fields work as long as the fields exist.

Because you cannot create unsupported fields using the QBL, tables that have these field types are likely to have a mismatch in field IDs between the QBL representation and the actual application. 

 

Unsupported properties:

  • Field caching for Summary fields
Pages
  • Exporting and updating solutions that contain legacy pages is not supported and will result in error
References References (!Ref) can only refer to objects in the same application. They cannot refer to objects in the solution that are children of a different application.
Reports
  • Report caching
  • The format property in Table Reports
Roles Role permissions for unsupported objects. This includes the permission List this report in the panel for on reports and charts, and the option to specify a home page on pages and dashboards.

Related articles

Top