QuickBase Release Notes: January 22, 2012

Please note there is one revision more recent than the one you are about to edit.

Question: *

Vocabularies

Knowledge Base Categories: *

Tags:

A comma-separated list of terms describing this content. Example: funny, bungee jumping, "Company, Inc.".

Show summary in full view

Answer:

<p>
      In our January release, we have added several features to QuickBase. See the sections below for further information.
    </p>
    <ul>
      <li>
        <p>
          <a href="#new">What's New in QuickBase?</a>
        </p>
      </li>
      <li>
        <p>
          <a href="#fixed">What's Fixed in QuickBase?</a>
        </p>
      </li>
    </ul>
    <p>
      Do you have an idea for improving QuickBase?&nbsp; You can share your suggestions by either clicking the orange <strong>feedback</strong> tab on the My QuickBase page, or visiting the Customer Feedback for Intuit QuickBase forum (<a href="http://quickbase.uservoice.com/" target="_blank">http://quickbase.uservoice.com</a>).
    </p>
    <p>
      <a id="new" name="new"></a>
    </p>
    <h2>
      What's New in QuickBase?
    </h2>
    <p>
      The January 22 release introduces the following new features:
    </p>
    <ul>
      <li>
        <p>
          <a href="#mobileweb">Mobile Web Version of QuickBase</a>
        </p>
      </li>
      <li>
        <p>
          <a href="#testasrole">Hide "Test as role" Feature for Roles</a>
        </p>
      </li>
      <li>
        <p>
          <a href="#prsub">Personal Report Subscriptions</a>
        </p>
      </li>
    </ul>
    <p>
      You also can read about these features in the <a href="http://www.quickbase.com/help/" target="_blank">online help</a> after the release.
    </p>
    <p>
      We have also included some behind-the-scenes work in this release that lays the foundation for future UI improvements. To learn more about the changes, which are primarily of interest to account and application administrators, see <a href="knowledge-base/tell-me-more-about-ui-refresh-work-quickbase-will-be-releasing-starting-december-2011" target="_blank">the KnowledgeBase article on the topic</a>.
    </p>
    <p>
      <a id="mobileweb" name="mobileweb"></a>
    </p>
    <h3>
      Mobile Web Version of QuickBase
    </h3>
    <p>
      Mobile QuickBase is a mobile-friendly version of the QuickBase website that displays automatically when you open QuickBase in your mobile browser. Use the mobile site on your smartphone or tablet to view your applications on-the-go.
    </p>
    <p>
      We support the following mobile operating systems:
    </p>
    <ul>
      <li>
        <p>
          Apple iOS 3.1+
        </p>
      </li>
      <li>
        <p>
          Android 2.1+
        </p>
      </li>
    </ul>
    <p>
      For now, the mobile QuickBase site only allows viewing applications. You cannot modify applications within the mobile site, but you can switch quickly to the regular QuickBase site (called the <em>full site</em>) in your mobile browser for tasks such as editing or adding records, creating new reports, or modifying your application's structure.
    </p>
    <p>
      <a id="testasrole" name="testasrole"></a>
    </p>
    <h3>
      Hide "Test as role" Feature for Roles
    </h3>
    <p>
      <span class="inline-left inline">You can now choose to hide the "Test as role" feature from the User Interface for any role.&nbsp; If you hide the feature for a role, users in that role will no longer see the <strong>Test as role</strong> option in the <strong>Sign in</strong> <strong>as</strong> menu.</span>
    </p>
    <p>
      <span class="inline-left inline">Choose to show or hide the Test as role option by selecting</span> <span style="font-weight: bold;"><strong>Customize &gt; Roles</strong></span>, then choosing the role you want to edit. In the <strong>Menus</strong> section of the <strong>User Interface</strong> tab, show or hide the <strong>Test as role</strong> option for that role.&nbsp;
    </p>
    <p>
      <span class="inline inline-left"><span class="inline inline-left"><img class="image image-preview" src="http://quickbase.intuit.com/developer/sites/default/files/images/testasroleUIelement_0.png" border="0" height="388" width="306"></span></span>
    </p>
    <p>
      <a id="prsub" name="prsub"></a>
    </p><h3>Personal Report Subscriptions
    </h3><p>
      As requested on UserVoice, QuickBase users and application administrators may now create report subscriptions for personal reports.
    </p><p><span class="inline inline-left"><span class="inline inline-left"><span class="inline inline-left"><span class="inline inline-left"><span class="inline inline-left"><span class="inline inline-left"><span class="inline inline-left"><img class="image image-preview " src="http://quickbase.intuit.com/developer/sites/default/files/images/subscribe_personal.png" border="0" height="271" width="393"></span></span></span><br></span></span></span></span></p>
    <h2>
      <a id="fixed" name="fixed"></a>What’s Fixed in QuickBase?
    </h2>
    <p>
      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.)
    </p>
    <h3>
      Form UI Issues
    </h3>
    <table style="width: 637px;" border="1" cellpadding="1" cellspacing="0">
      <tbody>
        <tr>
          <td valign="top" width="159">
              <strong>Issue</strong>
          </td>
          <td valign="top" width="639">
              <strong>Description</strong>
          </td>
        </tr>
        <tr>
          <td valign="top">
            QBE001877, QBE004605
          </td>
          <td valign="top">
            Under some circumstances, it was not possible to remove a field from a form. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
            QBE004714, QBE005171, QBE005301
          </td>
          <td valign="top">
            When editing a record, the "?" Help icon displayed on a new line (instead of to the right of the field) when the Help property was defined for a reference field with a conditional behavior. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
            QBE005411
          </td>
          <td valign="top">
            Apostrophes did not display correctly for built-in fields on forms. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
              QBE005413
          </td>
          <td valign="top">
              Fields on a form were vertically middle-aligned when they appeared on the same row in a section that had been set to show field labels above fields. This issue has been resolved, and the fields are now correctly top-aligned.
          </td>
        </tr>
        <tr>
          <td valign="top" width="159">
              QBE005675
          </td>
          <td valign="top" width="639">
              Table headers in a record appeared above the grey overlay used when a record was being saved. This issue has been resolved.
          </td>
        </tr>
        
      </tbody>
    </table>
    <h3>
      <br>
      Grid Edit Issues
    </h3>
    <table style="width: 637px;" border="1" cellpadding="1" cellspacing="0">
      <tbody>
        <tr>
          <td valign="top" width="159">
              <strong>Issue</strong>
          </td>
          <td valign="top" width="639">
              <strong>Description</strong>
          </td>
        </tr>
        <tr>
          <td valign="top">
            QBE001765
          </td>
          <td valign="top">
              Conflict Resolution of edits to a proxy field in Grid Edit would not proceed after the user clicked <strong>Begin Conflict Resolution</strong>. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
              QBE004372
          </td>
          <td valign="top">
              The Grid Edit conflict dialog did not display large amounts of text gracefully, and the button to dismiss the error message was not accessible in this case. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top" width="159">
              QBE005470
          </td>
          <td valign="top" width="639">
              On Apple iPhones and iPads, checkbox fields could not be checked in Grid Edit. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
              QBE005533
          </td>
          <td valign="top">
              When using Grid Edit on multi-line text fields, line breaks were incorrectly treated as editing conflicts. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
             QBE005556
          </td>
          <td valign="top">
              When using Grid Edit on a proxy field that proxies for a text field, false editing conflict errors were reported. This issue has been resolved.
          </td>
        </tr>
      <tr><td valign="top">QBE005579</td><td valign="top">Editing a proxy field in Grid Edit resulted in a “Look-up fields are not
 editable” message if the source field in the master table was set to 
view only. This issue has been resolved.</td></tr></tbody>
    </table>
    <h3>
      <br>
      Summary Report Issues
    </h3>
    <table style="width: 637px;" border="1" cellpadding="1" cellspacing="0">
      <tbody>
        <tr>
          <td valign="top" width="159">
              <strong>Issue</strong>
          </td>
          <td valign="top" width="639">
              <strong>Description</strong>
          </td>
        </tr>
        <tr>
          <td valign="top">
              QBE003694
          </td>
          <td valign="top">
              In cross-tab summary reports grouped on a Formula - Duration field, that field sorted as text rather than numerically. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
            QBE005425
          </td>
          <td valign="top">
            In summary reports grouped on a Date/Time field, clicking through to view details of the groups did not display the individual records. This issue has been resolved.
          </td>
        </tr>
        
        <tr>
          <td valign="top">
            QBE005563
          </td>
          <td valign="top">
            In crosstab summary reports, using Combine on a Numeric field resulted in the report sorting as text rather than numerically. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top" width="159">
             QBE005619
          </td>
          <td valign="top" width="639">
              In cross-tab summary reports with row grouping by First Word, links to records in the row groupings did not work. This issue has been resolved.
          </td>
        </tr>
      </tbody>
    </table>
    <h3>
      <br>
      Other Issues
    </h3>
    <table style="width: 637px; height: 691px;" border="1" cellpadding="1" cellspacing="0">
      <tbody>
        <tr>
          <td valign="top" width="159">
              <strong>Issue</strong>
          </td>
          <td valign="top" width="639">
              <strong>Description</strong>
          </td>
        </tr>
        <tr>
          <td valign="top" width="159">
              QBE001863
          </td>
          <td valign="top" width="639">
              Reports with &lt;ask the user&gt; selection criteria for a Reference field returned no records if the user selected &lt;anything&gt;. This issue has been resolved; selecting &lt;anything&gt; now returns all records as expected.
          </td>
        </tr>
        <tr>
          <td valign="top" width="159">
              QBE004802
          </td>
          <td valign="top" width="639">
              Personal reports were not copied when you copied an application.&nbsp; This issue has been resolved; personal reports are now copied automatically when you copy an application.
          </td>
        </tr>
        <tr>
          <td valign="top">
            QBE005227
          </td>
          <td valign="top">
            When a role was denied access to a field, and another role allowed access to Everyone on the Internet, setting table-level access to None in the second role did not successfully bar a user in the first role from accessing the field denied to him. The issue was resolved by adding a <strong>No Access</strong> option for fields in the Role Permissions tab when customizing roles.
          </td>
        </tr>
        <tr>
          <td valign="top">
              QBE005244
          </td>
          <td valign="top">
              When creating an email notification in Chrome, and viewing <strong>Additional criteria</strong>, the checkboxes for notifying about specific field changes displayed by default, even though the <strong>When any field changes</strong> radio button was selected. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
              QBE005321
          </td>
          <td valign="top">
              The button names on the Confirm Navigation dialog in Chrome were not consistent with the dialog text. The Confirm Navigation dialog displays when you have unsaved changes and attempt to navigate away from the current page. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
            QBE005334
          </td>
          <td valign="top">
            Creating a sandbox, copying an application, and cloning an application did not retain the original application's current revision setting for an attachment field. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
            QBE005429
          </td>
          <td valign="top">
            Calls to API_GetRecordInfo were replacing newline characters (\n) in text fields with &lt;br/&gt; tags. This issue has been resolved; those characters now appear correctly as "&amp;#010;".
          </td>
        </tr>
        <tr><td valign="top">QBE005430</td><td valign="top">Extremely long formulas with syntax errors caused the formula syntax 
error dialog to display incorrectly. This issue has been resolved.</td></tr><tr>
          <td valign="top">
            QBE005465
          </td>
          <td valign="top">
            When entering email addresses to share an application with a new user, separating the email addresses by a semicolon and space caused duplicate users to appear in the email address field and to be created in the application. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
              QBE005529
          </td>
          <td valign="top">
              When creating or editing a report, it was possible to select fields that were not reportable for sorting, filtering, or display. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top" width="159">
              QBE005558
         </td>
          <td valign="top" width="639">
              The user status in SAML realms could be inaccurate and confusing.&nbsp; This issue has been resolved.
          </td>
        </tr>
        
        <tr>
          <td valign="top" width="159">
              QBE005580
          </td>
          <td valign="top" width="639">
              On forms in Safari for Windows, you could not pick &lt;Select another user...&gt; in a User dropdown.&nbsp; This issue has been resolved.
          </td>
        </tr>
        
        <tr>
          <td valign="top">
              QBE005613
          </td>
          <td valign="top">
              In Internet Explorer 7 and 8, if the Filter Criteria Builder included a date field as the second criteria, under certain circumstances you were unable to select a date.&nbsp; This issue has been resolved.
          </td>
        </tr>
        
        <tr>
          <td valign="top" width="159">
              QBE005618
          </td>
          <td valign="top" width="639">
              You were able to add duplicate fields to a form.&nbsp; This issue has been resolved.<br>
          UPDATE as of 1/31/2012: This QuickBase release has been patched to allow duplicate fields on a form when the field type does not allow data entry. For example, formulas, report links, and summary fields can now be duplicated on a form.</td>
        </tr>
        <tr>
          <td valign="top" width="159">
              QBE005620
          </td>
          <td valign="top" width="639">
              Advanced Find was not defaulting to the correct table if the first table in the application was hidden for the role.&nbsp; This issue has been resolved.
          </td>
        </tr>
        <tr><td valign="top">QBE005645</td><td valign="top">The <strong>Find &gt; Advanced Find </strong>menu option no longer appears when there are no tables visible.</td></tr><tr>
          <td valign="top" width="159">
              QBE005648
          </td>
          <td valign="top" width="639">
              The Exact Form custom code in the online help has been updated to prevent caching when loading reports.&nbsp;
          </td>
        </tr>
        <tr>
          <td valign="top">
              QBE005660
          </td>
          <td valign="top">
              The documentation did not clearly explain how sharing an application with "Everyone on the Internet" interacts with testing roles. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
              QBE005663
          </td>
          <td valign="top">
              In Safari, using the keyboard to navigate QuickBase menus closed the <strong>Find</strong> menu prematurely. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
              QBE005664
          </td>
          <td valign="top">
              In Firefox, selecting text or clicking in the Find field (available from the Find menu) using the mouse would fail. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
            QBE005666
          </td>
          <td valign="top">
            When resetting a password, you could enter one longer than 20 characters, but the QuickBase login screen did not recognize the longer password. This issue has been resolved, and 20 characters is now the maximum length for a password.
          </td>
        </tr>
        <tr>
          <td valign="top">
            QBE005685
          </td>
          <td valign="top">
            When access to applications in a QuickBase realm had been limited by IP address, and an API call originated from an IP address that was not allowed, QuickBase returned an "unknown" error. This issue has been resolved, and that error has been assigned error code 19 (Unknown IP address).<br>
          </td>
        </tr>
        <tr>
          <td valign="top">
            QBE005695
          </td>
          <td valign="top">
            When creating a new application, pressing Enter after typing the application name would cancel the action and display the My QuickBase page. This issue has been resolved; pressing Enter now correctly creates the application.
          </td>
        </tr>
        <tr>
          <td valign="top">
            QBE005700
          </td>
          <td valign="top">
            When placeholders were replaced with user data, the changes were not being saved. This issue has been resolved.
          </td>
        </tr>
        <tr>
          <td valign="top">
            QBE005704
          </td>
          <td valign="top">
            The <strong>Partners &amp; Add-ons</strong> menu option was missing from the <strong>Help</strong> menu. This issue has been resolved.
          </td>
        </tr>
        <tr><td valign="top">QBE005709</td><td valign="top">In some cases, form rules involving Duration formulas would not fire. This issue has been resolved.</td></tr>
      </tbody>
    </table>

Input format

Filtered HTML

Web page addresses and e-mail addresses turn into links automatically.
Allowed HTML tags: <a> <p> <hr> <br> <br /> <ul> <ol> <li> <dl> <dt> <dd> <table> <tr> <td> <em> <b> <u> <i> <strong> <font> <del> <ins> <sub> <sup> <quote> <blockquote> <pre> <address> <code> <cite> <embed> <object> <param> <strike> <caption> <img> <h1> <h2> <h3> <h4>
You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>, <c>, <cpp>, <drupal5>, <drupal6>, <java>, <javascript>, <php>, <python>, <ruby>, <xml>. The supported tag styles are: <foo>, [foo].
Images can be added to this post.

Plain Text

Web page addresses and e-mail addresses turn into links automatically.
Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>

More information about formatting options

Revision information

Log message:

An explanation of the additions or updates being made to help other authors understand your motivations.

QuickBase Release Notes: January 22, 2012

Browse by Category

Knowledge Base Categories

Formula Category

The QuickBase Blog

Online Database Software:

Company Information:

Site Links:

From the Makers of: