Knowledge Base

Our Knowledge Base covers a wide variety of technical topics, from the basic to the complex.

QuickBase Release Notes: February 20, 2011

We know you rely on data stored in your QuickBase apps to make critical business decisions. And, when you need data to support decision making, you need to access it quickly and easily. In our February release, we’ll help you do just that by introducing three new tools to make finding important data more intuitive. It’s never been simpler to create complex queries that enable you to drill down into specific data. We’re also giving app admins greater control over who can edit critical reports to simplify set up of reporting defaults. In addition, we’ve made it easier for users to identify records when adding or changing data by giving app admins the ability to customize Edit Record and View Record form headings.

And, we continue to make QuickBase more reliable and stable by fixing a number of bugs as well.

What’s new in QuickBase?

Create precise reports using ANY and ALL

In the Report Builder, QuickBase will now let you find data that meets ALL or only SOME of the filter criteria you specify. That means you can create more precise queries without having to write complicated formulas.

The new filter interface lets you select either ALL or ANY as operators that apply to a set of criteria, effectively creating AND and OR conditions within your query. You can create different sets of criteria, and can nest up to three levels.

Check out the example below. In an app that tracks real estate listings, this query finds all Single-Family homes in the MetroWest location with 3 or more bedrooms that have:

  • Either a basement or a garage

  • Either Southern Exposure AND Central Air conditioning OR no Southern Exposure

    Complex Query 

Watch how to create this query.

Top of page

Control who can customize your reports

App admins can get greater control over who can and cannot edit their most critical reports. You can now choose to hide the Customize This Report link from users in a particular role. (Set this option on the User Interface tab on the Roles page.) When you choose this option, users in the role won’t see the Customize this Report link on displayed reports, nor will they be able to right click to edit the report onscreen. This setting applies to all reports in the application, shared or personal.

Note: If you choose to select this option for a role, be sure to also hide all tables, as shown
in the illustration below. If you choose to hide only the Customize this Report link, users will be able to create reports that they can no longer edit.

Top of page

Set reporting defaults in one place

In previous releases, app admins could define the default columns used in QuickBase reports using something called the Default Report . In our February release, we’ve made it easier to access default reporting settings, consolidating these options on the Field list page for a table. On this page, you can tell QuickBase:

  • Which columns should be the default columns

  • The order in which default columns should be displayed

  • The field by which the report should be sorted and the default sort order

QuickBase uses the reporting defaults you specify when:

  • QuickBase displays results of any Find operation.

  • You display detail (or child) records by clicking a report link field in a master record.

  • You display detail (or child) records by clicking a summary field in a master record.

  • You embed a details table in an exact form.

  • You use the QuickBase API to return a report (API_DoQuery without specifying the clist parameter).

Top of page

Change the heading that appears when you view or edit records

We’ve gotten lots of feedback about the heading that appears on the forms used to edit and view records. In past releases, this heading was made up of:

  • The noun used to identify records in the table (for instance, Contacts, or Tasks)

  • The value in the key field (usually the record ID)

Your feedback told us that this was not always helpful—in some cases, you wanted to be able to use the value in another field, such as an invoice number, in place of the key field.

We listened to that feedback and, in the February release, app admins will see that they can define something called the Record Name for each table. The example below shows the edit record form if you've chosen Task name as the Record Name for the Tasks table:

Go to Customize table-> Properties ->Advanced Properties to access this feature. In the
Record Name field, simply select the field you’d like to use in place of the key field in the heading on the edit/view record form.

Top of page

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).




If a role was set up with table-level access but the Application level permission set to None, users could still access table-specific information in some cases. This issue has been resolved so that Application-level permissions set to None override any table-specific settings.

Note: If you use the QuickBase API to submit data to your app via a web form, you must ensure that the role used to submit the data has at least Basic Access application permissions. If the app level permission is set to None, you will receive an error message when data is submitted. Note that this includes scenarios where a “user agent” submits data on behalf of anonymous users, or where the data is submitted through the ”Everyone on the Internet” persona.


QuickBase did not allow you to convert a field to a lookup field. This issue has been resolved.


In Google Chrome, the wrong message displayed in the dialog box that displayed to warn users that they would lose changes if they navigated way from the Roles > Permissions page without saving. This issue has been resolved.


The API_GetUserRole call has been modified. If you use the inclgrps parameter, QuickBase will return all roles assigned to a user, including those assigned to a user because he or she belongs to a group. When you use this parameter, the response will identify the roles type; it will tell you whether the role is assigned to:

  • a user

  • a group

  • a domain group

See the QuickBase API Guide for more information and examples.


In Internet Explorer 7 and 8, an issue occurred when you configured a role’s permissions and set the fields to Custom Access. When you clicked Edit, the section that allowed you to set custom access for fields appeared far to the right. This issue has been resolved.


A problem occurred when you tried to add a record using a report link field that contained a formula-text field on a form through grid-edit. QuickBase would not save the new record and displayed an error. This issue has been resolved.


QuickBase displayed an error message that was not helpful when there was an error building a conditional dropdown. The error message has been changed to include more details about the problem.


The API_SetKeyField call returned a parsing error. This issue has been resolved.


App admins were not able to specify a field other than the key field to appear in the heading of Edit Record and View Record forms. This issue has been resolved. In the February release, app admins can go to Customize Table > Properties > Advanced Properties and choose a new field to appear in the Edit/View Record header using the Record Name field. (See the QuickBase online help for more information.)


When users tried to open a Microsoft Office document (using Internet Explorer 8 and Windows 7), they were requested to log in. This issue has been resolved.

Top of page


hiding 'customize' for reports

I was so excited to hear about this new feature...but it is not useful to me if it affects any/all reports - personal and shared.  Ideally, this functionality would exist per report.  So that company wide 'shared' reports that were created by management cannot be customized by anyone other than the creator of the report.  Can you please pass this feedback on to your product development team?

Thank You - Beth

Yes, I will indeed pass along

Yes, I will indeed pass along this feedback--thanks for reaching out!


Beth Favini

Senior Information Designer

Product enhancements feedback

There are a lot of enhancements that enhance the functionality of Quickbase. Especially the ANY/ALL feature. Now, can we use this while specifying the conditions for summary fields?

Currently, you can't use

Currently, you can't use ANY/ALL when specify conditions for summary fields--but I am forwarding this request over to our product management team for future consideration. Thanks very much for the feedback!

since upgrade field numbers have disappeared in ie7


Firstly the new features are great. But since the new realease when I go customise-tables, then view the fields in a table, I cannot see the numbers indicating the order to the left of the fields. If I order the fields in reverse numeric, or alphabetical, the field numbers come back.  I am running IE7, its only minor issue but I am mainly a developer and often when I am talking to my colleagues on the phone we refer to those numbers.


Peter Savage

Hi Peter,Thanks for letting

Hi Peter,

Thanks for letting us know...what you're observing is actually how the feature was designed....if you sort on the Order column,in ascending order, the numbers disappear, but QuickBase shows you the fields in order. So, the first field in the list is #1, second is #2, and so forth. And, in that view, you can drag and drop to reorder fields.

If you need to refer to order number when talking to a colleague, you can sort on any other column, or on the Order column in descending order. In that view, you'll see the default column order.

Will that work for you?


Thanks, It will do. You are

Thanks, It will do.

You are suggesting that the numbers were not there before the update(I must be losing it). I didnt realise I could drag and drop fields to re-order them. I assume that the FID's do not change?

Thanks Again

No, you are not losing it!

No, you are not losing it! The numbers were there before the release. But, because of a new feature introduced in the release, the numbers now don't display when you sort in ascending order by the Order column.

In the release, we consolidated default reporting settings onto the field listing page. Before the release, you had to access something called the "default report" to manage these settings.

You can read more about the feature here: and do let me know if you have any questions...but, because we now let you drag and drop to change the default order, we don't display the numbers in that view.

And, yes, you are right--the fids do not change at all--the numbers in the "Order" column simply reflect the order of the fields in relation to how they appear as "default columns" in reports.

I hope that answers your question--please do let us know if we can help further!


After Update - Error Code 22

If anyone is struggling with error code 22 from an api call on an html form on a web site.  Check your application - and make sure the "Every one on the Internet" user role at least has basic access.  It took me a little bit to find the issue - but it fixed it.

You're Listening!!! Yay

Great new features you're rolling out.


To make the removal of the 'Customize this report' feature, I agree with Sandy, we should still be able to show the table.



Passing feedback along to PM

Thanks for the feedback...I'm passing it along to our Product  Management team...but here are some tips on how to set up a role to use this option as it's implemented today:

1) If you don’t want users to find records ad hoc or build new reports from scratch, you’ll need to also select Hide Table in order to hide the table menus for the role. 

2) Make sure the Dashboard for the role either includes links to the reports
you want users in the role to see or the actual reports themselves. One easy way to do this is to make sure the Left Colum of the Dashboard is set to Show All Reports; this will ensure all reports you’ve given the role access to show in this list.  (You can change what reports a role has access to right above the Hide the customize this report link checkbox.)

3) If you still need users in the role to be able to add new records, be sure not to hide the default ‘Add’ button that normally shows on the top of reports.


Some great changes here!

feedback on upgrade

I really like the enhancement made to reporting!


My one disappointment was that, I initially was very excited about the ability to hide the "customize report" link, but I don't think it will be at all useful to us if we have to hide all tables to make it work right :-(



Thanks for your

Thanks for your feedback...I'm sorry to hear you don't think the "customize report" link will work for you--I'll be happy to send this feedback on to our Product Management team.

Nice job on the ANY and ALL

Nice job on the ANY and ALL !


Wow! I'm delighted to hear of these updates. Bring it on, QuickBase!

We Welcome the Filtering Enhancements

Thank You! The reporting feature will now have more utility for us with the filtering advancements. 

Nice Job

Wow - this looks like an excellent release with a lot of features that will make a difference right away. I especially like the "Record Name" feature!

Thanks for the release

Thanks for the report filter option and the heading change option in the edit/view form.

Please come up with some options with Summary report as well, like Coulmn label change, option of more cross tab(column grouping) etc.

Woot! Thanks for the great

Woot! Thanks for the great updates!

Control who can customize your reports

Thanks so much for this.

Create precise reports using ANY and ALL

Woot! Woot! Thank you! We have been waiting for this "OR" feature in report filtering for a long time! I'm very excited to test it out!

Great news on the new features.

I am glad to see some of my pet pieves finally corrected.  Showing the record ID (key field) for each record often created confusion for users.  Removing "Customize this report" will provide another option for security to hide confidential fields without removing access to the fields.  I just hope others requests do not take the 4 or 5 years that these did before being implemented.

Post new comment

The content of this field is kept private and will not be shown publicly.
Type the characters you see in this picture. (verify using audio)
Type the characters you see in the picture above; if you can't read them, submit the form and a new image will be generated. Not case sensitive.

© 1997-2014 Intuit Inc. All Rights Reserved.

Online Database VeriSign Secured Web Based Software TRUSTe Certification Online Database SSAE Audit