Knowledge Base

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

What are the most common QuickBase actions that can affect performance?

The table below describes some of the most common actions QuickBase performs and how they affect system performance. If you are trying to optimize performance in QuickBase, it’s helpful to understand these actions so that you can make any necessary adjustments.

Action

Description and recommendations

q

Name: Query

Description: Query a table using a shared, personal, or temporary report

Recommendations:

  • Be sure to order filter criteria in reports carefully. QuickBase processes filter criteria sequentially. Your reports should eliminate the most records with the first filters.

  • Try to use native data fields (from the table you are in) rather than derived fields like summary or formula fields. Derived fields must do additional queries, permission checks, and calculation before they can be evaluated against your query.

  • Wherever you can, use exact matches when building your filter criteria. Using IS as your matching operator will be faster than using Contains.

  • Limit the number of columns returned by your reports to display only the most important data necessary for the user to take effective action.

  • Use sorting and grouping only when absolutely necessary. Remember that sorting and grouping operations add handling time, especially for large results sets.

  • Dashboard

    Name: Application Homepage

    Description: Display one of the application dashboards (a.k.a. home pages)

    Recommendations:

  • Carefully manage the use of images on dashboards. If you
    are hosting the images in a QuickBase application, the system must check permissions for each image returned.

  • Carefully manage the reports used on a dashboard. Summary reports often take longer to return results because they have to poll the full contents of a details table to calculate summaries.

  • Carefully manage the number of rows and columns returned for reports that are on the dashboard. Remember that the dashboard is designed to help the user take fast action; it need not provide the full details of records in tables.

  • Carefully manage any additional HTML or scripting that may be in the dashboard HTML text sections. The actions of these scripts may cause unnecessary drains on system resources.

  • Use the Query best practices to optimize reports.

  • QuickSearch2

    Name: FIND records

    Description:Using the FIND menu, search one or more tables for records based on filter criteria; Uses Default column settings for results format.

    Recommendations:

  • Limit the number of fields that can be searched using "Some field" or "FIND" searches. Most users are searching for a specific piece of data that is predictable and knowable. Use that knowledge to restrict these searches to relevant fields only. Learn how to exclude fields from "Some field" searches.

  • Create 'Ask the user' reports to let users specify the data they want to see.

  • Be sure to order filter criteria in searches carefully. QuickBase processes filter criteria sequentially. Your reports should eliminate the most records with the first filters.

  • Try to use native data fields (from the table you are in) rather than derived fields like summary or formula fields. Derived fields must do additional queries, permission checks, and calculation before they can be evaluated against your query

  • Create custom search boxes on the dashboard that
    query a specific field for values submitted by the user.

  •  

    API_doQuery

    Name:  Execute API Query

    Description: Use the HTTP API language to query a table and return results

    Recommendations:

  • Be sure to order filter criteria in API queries carefully. QuickBase processes filter criteria sequentially. Your reports should eliminate the most records
    with the first filters.

  • Try to use native data fields (from the table you are in) rather than derived fields like summary or formula fields. Derived fields must do additional queries permission checks, and calculation before they can be evaluated against your query.

  • Use sorting and grouping only when absolutely necessary. Remember that sorting and grouping operations add handling time, especially for large results sets.

  • er

    Name: Edit a Record

    Description: Edit a record using QB form

    Recommendations:

  • Consider reducing the number of embedded report link fields on a form. These require additional handling time to poll detail tables and return related records.

  • Consider reducing the column choices of any embedded report link fields, using fewer formula and summary fields in your embedded table structure.

  • Consider reducing the number and complexity of any dynamic form rules present on the form.

  • Consider using links to additional forms for forms with more than 100 fields. Use additional 'sub' forms for managing a piece of the process. 

  • dr

    Name: Display a Record

    Description:View a record using a QB form

    Recommendations:

  • Consider reducing the number of embedded report link fields on a form. These require additional handling time to poll detail tables and return related records.

  • Consider reducing the column choices of any embedded report link fields, using fewer formula and summary fields in your embedded table structure.

  • Consider reducing the number and complexity of any dynamic form rules present on the form.

  • Consider using links to additional forms for forms with more than 100 fields. Use additional 'sub' forms for managing a piece of the process.

  • FinishEditRecord

    Name: Finish Edit Record

    Description: Commits a record to the database.

    Recommendations: This request can take a long time in two scenarios: 1) when there is a large file attachment, and 2) when there is a large number of email notification rules that need to fire once the edited record is committed to the database.

    GenAdvFind

    Name: Advanced Find

    Description: Presents users with the screen
    that lets them setup an "advanced find".

    Recommendations:  See the Query best practices for performance recommendations.

    API_GenResultsTable

    Name: Generate Results Table

    Description: Generates a table report without
    any of the QuickBase headers or footers. This is primarily used by people who want to embed a report on a web page.

    Recommendations: See the Query best practices for performance recommendations.

    API_GenAddRecordForm

    Name: Add Record Form Request

    Description: Returns the standard QuickBase new record add page (HTML) for the table whose DBID you specify. It contains edit fields for the user to fill and a Save button to add the record to the database. If you want to prefill any fields, you can do so by supplying one or more field/value pairs in the request. Any fields not prefilled or filled in by the user default to the values set in the table field properties.

    API_EDITRecord

    Name: Edit Record API

    Description:Changes any of the editable field values in the specified record. Only those fields specified are changed; unspecified fields are left unchanged.

    API_ImportFromCSV

    Name: Import

    Description: Adds or updates a batch of records in a database table. You can even do adds and edits together in the same API_ImportFromCSV request.

    API_GetSchema

    Name: API for Getting Schema

    Description: Returns metadata information about the QuickBase application, such as any DBVars created for it and all child table DBIDs as well.

    If you invoke this call on a table DBID, the DBVars are  returned. In addition,this call returns  table-related information such as queries,
    field IDs (fid), and the current property settings for each field.

    RecordPicker

    Name: Record Picker

    Description: Used to invoke the "record picker", which is the screen that is used when selecting a master record when editing a related details record.

    API_GrantedDBs

    Name: API for Getting List of Applications Have Access

    Description:Returns  the names and DBIDs of
    all the applications and tables that you are entitled to access. This call
    also returns a ticket. If you specify both parent and child tables to be
    returned, you can easily identify the parent from child by the database name
    that is shown.

    API_GetDBInfo

    Name: API for Getting Application Information

    Description:This request, when invoked on the application-level DBID or on a table DBID, gets the metadata information, such as the last time the table was modified. You might use this function to find out if the table has changed since you last used it, or to find out if a new record has been added to the table.

    TableDashboardUpdate

    Name: Dynamic Filter for Table Home Pages

    Description: Filters records on table home pages.

    Recommendations: This request can take a long time in few scenarios: 1) when there is a large large number of records on the table's home page, and 2) when a data-entry error has been made in a Date or Date/Time field. For example, if a date of "07-03-20141" was entered, QuickBase will scan ~20,000 years instead of the date range of <10 years likely intended.

    Comments

    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