302 Found

Found

The document has moved here.

Knowledge Base

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

QuickBase Release Notes: March 13, 2011

Our March release continues our theme of better QuickBase reporting, adding a feature that’ll help speed up and simplify report creation for your users.

What's new in QuickBase?

QuickBase now lets you limit the number of fields to choose from when building a report. This means that you can spend less time scrolling through fields that you won’t ever need for searching and reporting.

Make a field reportable

By designating a field as reportable, you tell QuickBase to make that field available in the Report Builder for filtering, sorting, and grouping reports. Making a field reportable also makes it available as a column that will display on a report.

Outside of the Report Builder, reportable fields are available in most places where you can specify filter criteria. That is, you'll be able to select reportable fields when you

  • perform an Advanced Find operation

  • specify additional criteria in Email Reminders

  • create advanced criteria in Email Notifications

When a field is NOT reportable, it won't be available in the filtering, sorting, or grouping UI in the Report Builder. You won't be able to select it to appear as a column in any report. And, it won't be available for filtering in any of the scenarios listed above.

Note that fields are marked reportable by default.

top

Automatically hide iCal, vCard, Report Link, and Formula URLs

There are certain field types on which you'll never need to filter, group, or sort: namely iCal, vCard, Report Link, and Formula URL fields. Because of this, these field types will NEVER appear in the field lists used for filtering, sorting, or grouping, regardless of whether you turn on the Reportable option or not.

top

What about existing reports?

If any of your existing reports filter, group, or sort on a field that is no longer reportable, the report will still work correctly. Fields that aren’t reportable will appear in red font in filtering, sorting, and grouping criteria, as well as in available columns.

Fields that aren’t reportable will remain in the report, notification, or reminder unless you change selections that use them. If you do so and save, the field that’s not reportable will not be available for selection the next time you modify the report, notification, or reminder.

Learn more

You can read more about the Reportable feature in the online help.

top

What’s fixed in QuickBase?

We’re continuing to focus on quality and have fixed a number of bugs in this release. You'll see these fixes when we release on 3/13/2011.  (As always, all QuickBase releases include bug fixes from previous releases).

Javascript issues

Issue

Description

QBE001910

A javascript error occurred when you tried to customize a report using the Customize this Report link where the following advanced options in the Report Builder were both unchecked: Show Main table and Show Summary table.  QuickBase now requires you select one of these options to save a report. QuickBase also requires that you choose a field for grouping if you choose Show Summary table.

QBE004835

If a form contained a portion of a conditional dropdown (i.e, contained the dependent, but not the master field), a blank form was displayed and a javascript error occurred.

QBE004882

A problem occurred if you created a formula URL field that contained javascript used to open the page in a new window. When users clicked the field, the browser showed a blank page.

QBE004883

When you clicked the Preview button on the UI Tab of the Manage Realm page in Internet Explorer (IE) 8, a javascript error occurred.

QBE004902

On the iPad/iPhone/iPod touch, if an app menu bar contained more tables than could display on one screen, the table menu bar extended beyond the size of the screen, causing you to have to scroll horizontally to see all tables. This behavior is now the same as on a desktop browser; QuickBase displays an .etc dropdown, allowing you to view the tables without scrolling.

QBE004926

A javascript error occurred in IE 8 when you clicked the application link for a user (in the dialog that appears when you choose Manage Billing Account > Users With Access and click the Apps link for a user.)

QBE004994

A javascript error occurred on the final page of the Create Relationships wizard while creating a cross-application relationship.

QBE005017

Reports formatted as XML and using an XSL stylesheet where the stylesheet was a dbpage displayed as a blank page in Windows Safari.

QBE005019

A javascript error occurred when the Resource Allocation Tool was used.

top

 

General issues

Issue

Description

QBE005022

The Find a Developer link in the Application site map went to the wrong site.

QBE005054

For QuickBase Enterprise only: The Performance Bar incorrectly displayed Version IE 7.0 in IE 8 browsers.

QBE005135

If a user was created recently and the user’s email address contained an apostrophe, it may have been stored incorrectly.  QuickBase didn’t properly display it on the Users With Access page and they did not receive email reminders or notifications.  Going forward, email addresses containing apostrophes should be created correctly.  If you see a problem with one on your Users With Access page, please contact support to have it fixed

QBE005137

If a table was hidden from a user, or if the user had no access to any reports in a table, the user was still able to see the table name on the left of the application dashboard.

QBE005197

Users using the Safari browser were unable to sign up for a QuickBase plan or change their credit card information.

QBE005215

The API_GetAncestorInfo call had been removed from the QuickBase API. It has been restored.

QBE005218

The Edit Contact Preferences link in the user profile now links to a new Manage Your Subscriptions page.

QBE005228

The API_GetUserRole call required users to have Sharing or Full Admin permissions.  In this release, users who do not have Sharing or Full Admin permissions can use this call to get their own role only. Sharing/Full Admin permissions are required to return the roles of other users.

top

Comments

Reports on the left side of the Dashboard

What happened to all the reports on the left side of the dashboard?  Some roles do not have direct access to the table, but they do have many reports available to them.  All the reports have disappeared.  Does this mean I need to give the role direct access to the table for them to see the reports on the left side of their dashboard?

Theresa

Hi Theresa,Thanks for letting

Hi Theresa,

Thanks for letting us know--this issue has been brought to our attention and we're fixing it in a patch, scheduled to be deployed tonight. Don't modify your role, but instead, wait until tomorrow--the reports should display as expected on 3/15. I'm sorry for the inconvenience.

Upgrade is a Downgrade

Would it be possible for the designers at QB let users know ahead of time what the new changes are so that we can make sure that your upgrades don't downgrade us?

Its starting to sound like the Cloud can just drop you out if it feels like it.

I feel that it is insane to make anything inaccessible to administrators.  I guess it is accessible if you leave it as reportable so I pull back my fangs.

In general we try to give a

In general we try to give a week's notice for new optional features -- the case in this release.  (If do we have to make a change that requires action on the part of customers, such as a security policy change, we give several weeks or months notice.)

What you say at the end of your comment is correct -- the new "reportable" feature shouldn't be changing anything underneath an administrator since it only goes into effect if an administrator changes field settings.  In addition, even if you mark a field not reportable but it is used in an existing report, that report won't be impacted unless the settings that use those fields are explicitly modified.  I hope this reassures you.

 

Reportable Property

I must admit that this is a great feature. There used to be situations, when we (Admin/Developers) used to create several hundreds of formula fields meant for our use but used to appear on the report builder and it was difficult to tell the users not to use them, without knowing what they are meant for.

At first when I saw the first few lines of this feature, it sounded great. Like, "here is the feature I have been desperately waiting for. But after reading the entire feature, it did not seem to be quite the answer to my issue at hand.

If only, there was role based permissions built around it, so I can clearly specify that it is reportable for application administrators and not for the users. I am sure, that will complete the story.

I wish I was there at the product designing table! ...Just kidding.

Keep up the good job, Quickbase!

Thanks for the feedback! In

Thanks for the feedback! In this release, the reportable feature is not role-based--if you make a field "reportable," it is reportable for everyone.

I will indeed forward this feedback on to our Product Management team (so, in a way, you will be at the product designing table!)....thanks once again for letting us know....

Great feature but need the fields to show for Administrators

Sounds like a great new feature -- I can see how it will help users tremendously as I have previously labeled fields as DO NOT REPORT so they weren't used incorrectly.

However, administrators will need to see these fields on reports for debugging and testing purposes - will the fields still be available for administrators to view and use in reports?  or some other way to facilitate the testing process?

Hi Dawn,Right now, the

Hi Dawn,

Right now, the reportable feature applies to all users...so there is no way to make a field "reportable" for administrators, but not for other users. I will indeed forward the feedback to the Product Management team for consideration, moving forward.

Thanks for reaching out!

 

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.
302 Found

Found

The document has moved here.