7.23.23
Contents
New
Quickbase acquires Fastfield
You may have heard the exciting news—Quickbase acquired Merge Mobile, whose flagship product is Fastfield. Fastfield is an intuitive, easy-to-use form builder that simplifies data entry. With this acquisition, Quickbase provides complete coverage between back-office operations, folks on the go, and field services. We are excited to release the first phase of our integration for joint customers.
Beta
As of 7/14, a Quickbase connector is now available in open beta in Fastfield within Integrations and Global Workflow.
Builders can map fields from Fastfield to Quickbase. This integration supports most field types. Additionally, parent-child relationships are supported to send a form and sub-forms from Fastfield to Quickbase.
Generally available
Starting 7/28/2023, the first phase integration will be made generally available. Additionally, builders inside of Fastfield will be able to import their Quickbase schema into Fastfield, simplifying the form creation experience.
Over the coming months, we’ll share further information on integrations and how you can learn more.
Enhancements
Performance update
We are constantly working to enhance the performance and user experience of Quickbase. In recent years, we have invested in rebuilding the foundational components of the Quickbase UI, such as table reports and forms. Now, we are leveraging our new architecture to improve the speed of navigating between these pages.
Starting this month, you will notice a change in the structure of URLs on these new pages. For example, apps that use the latest versions of table reports and forms will have a new path in the URL after the DBID. For example:
https://yourrealm.quickbase.com/db/{{dbid}}/form?a=dr...
You will not be required to update any of the URLs in your apps, and we’re maintaining compatibility with the old URL format.
These changes will be implemented in stages, and this list will help you know when they will be available in your account. However, be aware that these dates are subject to change.
| Realms beginning with | Anticipated rollout date |
| A-D | 7/24/2023 |
| E-M | 7/31/2023 |
| N-S | 8/7/2023 |
| T-Z and all others | 8/14/2023 |
Forms updates
New ways to add related data
In line with our continued investments, we’re making it easier for you to create and update records displayed in embedded reports when using new forms. Later this month, all users will be able to edit or view records displayed in embedded reports through a subform without leaving the page. You can also create new records using the New Record button in the header. You can leverage this behavior to:
- Quickly edit a related record
- Make edits to many records in sequence using the Save & Next button
- View or present records in sequence using the Next/Previous buttons
- Create new records on-the-fly, without leaving the page.
You don’t need to do anything to see these changes in your apps. If both forms use the new experience, you will be able to create, edit, and view records without leaving the page.
Builders can optionally choose to override this experience in the settings of the Report component. Here, they can choose to open the record in a new page, select the form to use when opening the record, and allow/prevent creating new records.
Copy forms
Builders can now copy forms from the forms list. To do this, navigate to the table settings, open the Manage Forms page, and click the Copy icon at the end of the row.
Select all fields
To help our builders get up to speed quickly using the new form experience, they can now add all fields in their table (up to the 500 limit) to the form at once.
Updates to tab width
Tabs now automatically size to fit the full width of the label.
Report actions for embedded table and timeline reports
We’ve added two new options to the toolbar for the report components for table and timeline reports:
- A quick link to open the grid edit version of a report in a new window. This will help you to quickly do edits of the related records embedded in the form.
- You can download the contents of an embedded report as a csv file. This will help you to easily share the data within the embedded report.
The filters and search criteria applied will be preserved when any of the options are used.
Additionally, we’re introducing a setting for report components to hide this toolbar to preserve space.
Showing conflict between form rules
To help our builders build form rules, we now show conflicts between actions of the form rules. This will lower the barrier for builders to extend the business logic inside their forms.
Enhanced otherwise section for form rules
Builders now have a quick way to see what the opposite behavior of their form rules in detail is.
Mobile dashboard enhancements
The following enhancements were released in the latest mobile app version 1.51, available in Google Play and App Store as of 6th July. Additionally, we have introduced performance improvements within the dashboard experience.
Pull to refresh
You can now use the pull-down gesture on the mobile dashboard screen to trigger a page refresh and get an updated version of their dashboard data.
Rich Text height mapping changes
The height of a rich text widget on a mobile dashboard depends on the widget’s height in the desktop's dashboard grid. One grid cell on desktop is equal to 20% of maximum widget height on mobile.
| Desktop grid cell | Widget height on mobile |
| 1 grid cell | 20% of maximum widget height |
| 2 grid cells | 40% of maximum widget height |
| 3 grid cells | 60% of maximum widget height, etc. |
Read more in Add a rich text widget.
Deep links to a mobile dashboard are now supported
When you tap on a dashboard link on their mobile device or scan a QR code containing such a link, you will now be brought to the dashboard screen in the Quickbase mobile application.
Monthly scheduled refreshes for connected tables (Quickbase Sync)
When setting up an automatic refresh schedule for a connected table, you can now use the new Every month option to schedule the refresh for a specific day each month.
User registration link expiration time setting
Now you can set an expiration timeframe for user registration links. You'll find the option on the Policies page in the Admin Console, under Security Policies. By default, links are active for 7 days.
Solutions Versioning updates
Blocking version restore when no common resources (apps/pipelines) exist
You won't be able to initiate version restores when there are no common resources (apps/pipelines) in the schema of the solution. If you try to restore a version with no common resources, you will now receive an error message and would not be able to proceed.
Beta opportunities
A new Quickbase Exchange experience
A new, more powerful Exchange is here! We’re excited to announce that the beta version of our enhanced Exchange is available to all customers. You can access the new Exchange via the app bar next to My Apps, Pipelines, and Solutions:
- Our vision for the Quickbase Exchange remains the same: It’s a destination to discover what’s possible and jumpstart your building with resources from Quickbase and the community. But we’re adding exciting functionality to help you go further, faster.
- For the first time ever, you’ll be able to find formulas in the Exchange. And there’s a lot more to come.
During this beta program, you can:
- Browse template apps and formulas
- Install or copy formulas with the click of a button
- Submit your own apps and formulas
- Provide feedback and help shape the future of the Exchange
| FEATURE | DESCRIPTION | STATUS | HOW TO PARTICIPATE |
| Pipelines Designer |
The latest updates in Pipelines Designer bring a range of new features, including an infinite canvas workspace, an enhanced step configuration process, the ability to rearrange steps using drag-and-drop, a new code editor, a step reference validator, and numerous other additions. |
Public Beta July 23 |
What’s fixed in Quickbase
| ISSUE | AREA AFFECTED | WHAT WAS BROKEN | WHAT WE FIXED |
| QBE018036 | Mobile | If you attempted to upload and save a file attachment in a form, you were redirected to the application's dashboard without saving the file attachment. |
This issue is now resolved in version 1.51 of the Quickbase mobile application.
|
| QBE017623 | Pipelines | Fields with longer than average field names could overflow beyond their container element(s) in the Pipelines builder UI. There were two places where long field names appeared to cause issues.
|
The issue is now resolved |
| QBE018089 | Reports - Builder 2.0 | When in Cards section and you chose Custom sort, and then backspace to delete, the focus was lost instead of being on the next available element. | We now set focus to next or first field after deletion of an item in the cards detail fields options. |
| QBE018090 | Reports - Builder 2.0 | You could see an error in the filters section and in dynamic filters/sorting sections if you selected a 'custom' radio button. | We now ensure that interactive controls are not nested as they are not always announced by screen readers or can cause focus problems for assistive technologies. |
| QBE018091 | Reports - Builder 2.0 | A screen reader announced the formula in the formula editor twice when the formula editor wrapper was focused. It happened on formulas with an error. Instead of repeating the formula, it should announce that "there is an error in the formula in the first formula editor” so the users know there is an error while navigating the elements in the formula section. |
When the formula editor wrapper is focused using the screen reader command, it now announces:
|
| QBE018123 |
Reports - Builder 2.0
|
Screen reader users needed to navigate the vertical panel sections, which was a gap in the builder panel. |
Aria labels are now read while users navigate the toolbar, so that they understand which panel section they are on. |
| QBE018151 | XML API | The response for calls made to API_FieldAddChoices returned the full count of choices, even if none were added to the default user set. | When updating the default user list using API_FieldAddChoices, we won’t return the number of choices added |
| QBE018019 | Forms 2.0 | New forms containing a duration type field that is used as a reference proxy displayed the duration in Unix/epoch time. |
New forms containing a duration type field that is used as a reference proxy will display the duration correctly. |
| QBE018042 |
Forms 2.0
|
New form rules forcing changes to multiple choice type fields for "value in the field" limited options to other multiple choice fields | The user can select a variety of field types to acquire the multiple choice value. |
| QBE018048 | Forms 2.0 | Percent fields (numeric as percent) on new forms displayed with a default value of "0 %". This default value affected user inputs. If the user clicked on the right of the default value, keying in a "4" resulted in a "04 %" value. If the user clicked on the left of the default value, keying in a "4" resulted in a "40 %" value. | User input has been corrected. |
| QBE018050 | Forms 2.0 | When you created a new form and had a form rule that hides other fields based on when a date field it blank, and you added another action after saving it, it broke the form rule and replaced the date field with a single quotation. | Adding another action to a form rule that previously used a date field no longer breaks the form rule. |
| QBE018062 | Forms 2.0 | If you created a form rule and in the condition, you left it blank, and then saved and reentered the form rule, the blank box updated to have a different entry. |
User input has been corrected.
|
| QBE018064 | Forms 2.0 | If you embedded a report on a new form and added a normal checkbox field below it, clicking the checkbox selected all records in the embedded report. | This action does not select all records in the embedded report. |
| QBE018065 | Forms 2.0 | When you pressed the Done button without making modifications to an existing form rule, the rule's status updated to "Pending Save". If you navigated away from the page an alert displayed, warning the you of potential lost changes. | User input has been corrected. |
| QBE018071 | Forms 2.0 | When you had a form rule set to "Clear a field" and "Display a Message" if the conditions were unmet, the system only cleared the field and didn't show the message. This occurred in all 3 types of messages (Modal, Notification, and field messages). | This behavior has been corrected. |
| QBE018076 | Forms 2.0 | A button on a new dashboard set to direct to a record displayed as a new form and set to redirect back to the dashboard instead redirected to the table's home page. | This behavior has been corrected. |
| QBE018078 | Mobile | The hamburger menu on a Dashboard screen was not fully scrollable. | You can scroll the full hamburger menu content. |
| QBE018079 | Forms 2.0 | In new forms, an embedded calendar report did not show weekend days. On the full report the weekends appeared as expected. | Weekends now display correctly. |
| QBE018084 | Forms 2.0 | For numeric fields deriving values from a predefined list, the available options always sorted in ascending lexicographic order. This was the case even when all options were numeric and when a descending order was specified at the field level. | Sorting can now be based on numeric values. |
| QBE018096 | Forms 2.0 | New forms with logged text fields sometimes did not respect the field's defined logging options. | Logging now works correctly. |
| QBE018098 | Forms 2.0 |
You were not able to drag a field from a tall column to a short column. |
This behavior has been corrected. |
| QBE018108 |
Forms 2.0
|
If you created two fields and grouped them together and then made one of them required by using a form rule, you could still save the record even if the field value is blank. | This behavior has been corrected. |
| QBE018109 |
Forms 2.0
|
If you modified a form rule's name/title, the "Done" button would remain inactive. | This behavior has been corrected. |
| QBE018128 |
Forms 2.0
|
In the new forms, a rich text field could not be actioned to change to a manually entered value using form rules. | This behavior has been corrected. |
| QBE018129 | Bulk record upsert | Bulk record upsert was permitted when testing as a user. | Bulk record upsert is not permitted when testing as a user. |
| QBE018139 |
Forms 2.0
|
When a button is placed on the form, Quickbase automatically added {{https://}} which messed up the execution of the code. | When the button is placed on the form, we don't add {{https://}}. |
| QBE018140 | Forms 2.0 | The address lookup field displayed a blank value. | The address field now displays the value on the form. |
| QBE018086 |
Forms 2.0
|
When you changed the date/time type field to date type, it retained time on the form. |
When you change the date/time type field to date type, your time is displayed on the form. |
| QBE018087 | Forms 2.0 | If you had "Show in User Pickers" disabled, the user would still show in new forms user pickers. |
This behavior has been corrected. |
| QBE018142 | Forms 2.0 | The dynamic form rule did not work correctly for conditional drop downs. |
The dynamic form rule now works correctly for conditional drop downs. |
| QBE018143 |
Forms 2.0
|
The Done button stayed inactive even after making changes to a "display message" rule with "filed" type. |
The Done button works as expected after making changes to a "display message" rule with "filed" type. |
| QBE018136 |
Pipelines |
In the ServiceNow channel, the Task, Incident, or Change Management tables could not be selected from the ServiceNow table selector. |
This behavior has been corrected. |
| QBE017767, QBE018110 |
Pipelines |
In the Jira Channel, you couldn't display multiple users in a field within a Jira Pipeline |
This behavior has been corrected. |
| QBE018144 |
Pipelines |
In the JSON Handler, you couldn't iterate over JSON records, and an unexpected validation error displayed. |
This behavior has been corrected. |
| QBE017987 |
Pipelines |
Pipelines does not get the correct value from a formula numeric field. |
This behavior has been corrected. |
| QBE018110 |
Pipelines |
In the jira channel, the multi-user picker field in the Issue resource currently you can only select one value while the JIRA API requires list of values. |
This behavior has been corrected. |