Release date: May 19, 2024
This article documents the changes made in QBL v0.3, the objects this version supports, and unsupported elements.
Change log
This release includes support for:
Application variables
Application variables were added as a QBL object. View the properties for application variables.
Audit logs enabled property for non-formula fields
The IsAuditable property is now available for these fields:
Checkbox fields
Currency fields
Date fields
Date created fields
Date modified fields
Date/time fields
Duration fields
Email fields
File attachment fields
Last modified by fields
List user fields
Multi-select text fields
Number fields
Percent fields
Phone number fields
Predecessor fields
Rating fields
Record owner fields
Reference fields
Rich text fields
Text fields
Text - multi-line fields
Text - multiple choice fields
Time of day fields
URL fields
User fields
Work date fields
View the properties for fields.
Mention users property on rich text fields
The AllowMentions property is now available on rich text fields. When on, this property allows users to mention others on rich text fields in new forms. A builder can then set up a custom email to notify people when they are mentioned. Learn more in May 2024 release notes, or view the properties for rich text fields.
Updates to KeyField property in Tables
In QBL v0.2, the key field property in tables was KeyFieldID, and it was not required. As of v0.3, this property has been updated to KeyField and it is now required. View the properties for tables.
Supported objects
These objects are supported in QBL v0.3:
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 |
---|---|
Temporarily unsupported:
Unsupported app settings:
| |
Fields and formula fields | Unsupported 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:
|
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. | |
Cross-app relationships. For example, table to table relationships that connect tables in different applications are not supported. | |
References ( |