QBL version 0.5 overview

  • 1 minute(s) read
Prev Next

Important

This version of QBL is no longer supported. Learn more about QBL versions.

Release date: December 16, 2024

QBL version 0.5 only supported these APIs:

It was not supported when updating solutions, or listing solution changes.

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

Change log

This release includes support for legacy forms. View the properties for legacy form elements and dynamic form rules.

Supported objects

These objects are supported in QBL v0.5:

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

Charts

 

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

Legacy forms and dynamic form rules

 

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.

Relationships

Cross-app relationships. For example, table to table relationships that connect tables in different applications are not supported.

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.

Tables