2.20.11 QuickBase Release: New Reporting Tools

Quick Base News
Feb 20, 2011
8 Min Read

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?

  • Users can create precise reports using ANY and ALL
  • App admins can control who can customize reports
  • Set reporting defaults in one place
  • Change the heading that appears when you view or edit records

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
  • Southern Exposure AND Central Air conditioning
  • No Southern Exposure


Complex Query

Watch how to create this query:

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.


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

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.

Recomended Posts