Our Knowledge Base covers a wide variety of technical topics, from the basic to the complex.
Knowledge Base
QuickBase Release Notes: September 11, 2011
In our September release, we have added several features to QuickBase. See the sections below for further information.
Do you have an idea for improving QuickBase? You can share your suggestions by either clicking the orange feedback tab on the My QuickBase page, or visiting the Customer Feedback for Intuit QuickBase forum (http://quickbase.uservoice.com).
What's New in QuickBase?
The September release introduces these new features:
You also can read about these features in the online help after the release.
New password requirements
We've strengthened the requirements for passwords used to access QuickBase, both on www.quickbase.com and on realms where users log in using QuickBase authentication. As a result, you'll be required to choose a password 8-20 characters long that contains both numeric and non-numeric characters, if your password doesn't already comply with those requirements. We've also improved the interface to show the requirements and the strength of the password you choose.
New security question requirement
We now require all users (on www.quickbase.com and on realms where users log in using QuickBase authentication) to set a security question and answer. This information is used as part of the password reset process, to verify your identity.
These features are part of our efforts to continually improve QuickBase security. Read more about the new requirements in the KnowledgeBase article: Tell me more about the new security requirements included in the September 2011 release.
QuickBase now displays 14 digits by default for decimal numbers
For numbers with decimal places, QuickBase now displays up to 14 digits in total if you do not specify a value in a Numeric field’s Decimal Places setting, and is consistent with the API_DoQuery API call. You can still override this default behavior by specifying a number of decimal places to display.
Documentation improvements
For the September release, we improved our reporting documentation by adding a new "Common Reporting Needs" topic to the online help. This topic describes how to create reports that meet common needs, such as reporting on data in multiple tables, reporting on projects and workflow, and creating reports that summarize data for specified time intervals.
We also improved the formatting of the QuickBase HTTP API Guide to reduce the PDF page count.
What’s Fixed in QuickBase?
We’re continuing to focus on quality and have fixed a number of bugs in this release. (As always, all QuickBase releases include bug fixes from previous releases.)
Issue | Description |
|
QBE001970 |
A conflict resolution message appeared when you saved Grid Edit changes. This issue has been resolved. |
|
QBE005125 |
In detail table reports that asked users to select a value from a lookup field, the lookup field did not contain values from the master table. This issue has been resolved. |
|
QBE005421 |
If the application owner no longer had permission for a table that triggered an email notification, the notification showed the current user as the owner of the application. This issue has been resolved; the email notification contains a warning if the owner no longer has access to the table that triggered the notification. |
|
QBE005445 |
Users on the Deny List for a billing account appeared in the user list in Address Book and User Picker for that account's applications. This issue has been resolved and denied users are no longer auto-suggested in the Address Book and User Picker. |
|
QBE005472 |
If you had a form rule set up to trigger a change based on a predecessor field not being empty, the rule did not trigger in real time if you chose the predecessor by using the "Add Predecessors" button. This issue has been resolved. |
|
QBE005479 |
A personal report showed up with a different owner. This issue has been resolved. |
- 21876 reads
Rate This
Similar Articles
Browse by Category
Knowledge Base Categories
- Accounts (35)
- Application (45)
- E-Mail (7)
- Fields (41)
- Forms (20)
- Formulas (18)
- General (68)
- Other Product (7)
- Pages (1)
- Product (5)
- Reports (15)
- Roles (4)
- Search (1)
- Tables (6)



Comments
Decimal places displayed in a report
The report total for the "average number of days" displays decimal places out to 14 digits; however we want to round it to to "0" decimal places. Can this be set for a specific report, or does it have to be set at the field / properties level, and thus display for all reports using that field?
Thank you,
re: decimal places
The easiest way of specifying the number of decimal places is to set it in the field properties -- that way you can be sure that the display will be consistent in all locations. The number of decimal places in the averages displayed in reports will depend on how many decimal places are used across all records in the table.
Thanks for writing!
--Sybil
Post new comment