This document describes our September 13, 2015 QuickBase release.
Do you have an idea for improving QuickBase? You can share your suggestions by either clicking the orange feedback tab on the My Apps page, or visiting the Customer Feedback for Intuit QuickBase forum (http://quickbase.uservoice.com).
What's New in QuickBase?
This section describes the changes that appear in QuickBase for the September release.
Address Field & Map Report Enhancements
There is a new form element property for Address fields that hides the map normally displayed along with an Address field. This property defaults to unselected. (QBE009598)
![]()
The map report now contains an enhanced popup for addresses with more than one associated record. (QBE009905)
![]()
Charting Enhancements
Bar and pie charts may now be sorted by labels or by values.
There is a new Sorting section for charts in the Report Builder. This section takes the place of the individual Display from fields. This section will also show Series Direction if you choose a field for the chart series.
![]()
The chart legend has new default colors. These colors will appear on new reports. Existing reports will not be changed. The color chooser is now the same as the one used to choose branding colors for the app.
![]()
There are now 16 unique colors in a chart’s series. (QBE009775)
Report Builder Enhancements
Choosing Save > Save as now appends copy to the report name.
Report names are now checked for duplicates, and duplicate report names are not allowed.
There is now inline validation and error reporting for fields in the Report Builder.
![]()
Copy Form Rules
You can now copy a form rule.
Changes to Add Record button behavior
The mobile site now respects the button setting Return to this page when adding a new record from an app home page. In this case, it will redirect to the home page after saving the record, as the desktop site does. (QBE010153)
What’s Fixed in QuickBase?
We’re continuing to focus on quality and have fixed a number of bugs in this release. All QuickBase releases include bug fixes from previous releases.
Issue ID | Description |
QBE001470 | Using a Date field as the series in a chart caused a “Too Many Legend Values” error message, and the field could not be grouped by anything other than Day, even if that grouping would reduce the number of legend values. This issue has been resolved. |
QBE001631 | Pie charts that used a calculated column as a filter did not display colors in the Legend area while customizing the report. This issue has been resolved. |
QBE004139 | When the account’s properties did not allow external email to be sent, and someone attempted to send email to a group, QuickBase displayed an error about emailing verified users only, even if all members of the group were verified users. This issue has been resolved. |
QBE004520 | An outdated message appeared when using the New table based on this column command to convert a field to a new table, if that field had been used in dynamic form rules. This issue has been resolved. |
QBE009488 | Category labels and Data values headings on horizontal and stacked horizontal bar charts referred to the wrong axes. This issue has been resolved. |
QBE009719 | Creating an app from scratch using the Spreadsheet method didn’t create a default home page for the new app. This issue has been resolved. |
QBE009813 | When choosing Custom columns for a timeline report, changes to the list of columns were not saved. This issue has been resolved. |
QBE010092 | When a dynamic form rule was used to display a message, and the field referenced in the rule was also referenced in a Formula field, the message displayed twice. This issue has been resolved. |
QBE010120 | Numeric - Percent fields did not display correctly on a gauge chart. This issue has been resolved. |
QBE010122 | For all chart types except the pie chart, the maximum number of legend values was not specified in the “Too Many Legend Values” error message. This issue has been resolved. |
QBE010158 | The sample response shown in the API_DoQuery documentation differed from the actual response value. This issue has been resolved. |
QBE010164 | A form on the mobile site became unresponsive due to a JavaScript error when a form rule set a read-only field to be required. This issue has been resolved. |
QBE010165 | Form rules did not work on the mobile site when the user’s role had Custom Rule set for modify record permissions. This issue has been resolved. |
QBE010168 | The ampersand (&) character appeared as& in form rules. This issue has been resolved. |
QBE010169 | File Attachments compared to a blank value using a dynamic form rule produced inconsistent behavior; the rule was applied when the record was viewed but not when it was edited. This issue has been resolved. |
QBE010171 | The cursor did not automatically appear in the data entry field when a report configured to <ask the user> displayed. This issue has been resolved. |
QBE010172 | Charts did not display the last zero for Numeric fields with decimal places. This issue has been resolved. |
QBE010177 | If the number format for an app was set to “12.345.678,00” or “1.23.45.678,00”, chart reports did not show any values on the Y axis. This issue has been resolved. |
QBE010192 | If the number format for an app used a period as the thousands separator, scatter, line/bar, and bubble charts would truncate the charted values just before the second period in the number. This issue has been resolved. |