Skip to Navigation

Field Types

Syndicate content

QuickBase includes a lot of detail in its URLs, which you can take advantage of when building formulas or external API functionality. For example, let’s consider a URL a user might see when viewing a report:

February 5th, 2015 - 5:02 PM

Let’s say you have a table for Products, another table for Line Items, and a relationship between the two where the product table is the master.

September 11th, 2014 - 9:09 AM

Before the release of address fields, you may have created several separate fields to capture address information. For example, you may have the following fields:

October 28th, 2013 - 4:10 PM

If you have recently upgraded to Windows 7 and Office 2010, attempting to open QuickBase file attachments saved in earlier versions (97-2003) of Excel, Word, or PowerPoint may produce this error. To fix the problem:

January 9th, 2012 - 10:01 AM

If you create a formula numeric type of field, you can reference the built in field Record ID # to increment your number automatically. If you're not familiar with creating new fields, please see our Add a New Field help topic.


June 23rd, 2009 - 9:06 AM

Append fields can become quite large and contain too much text to display in a report easily. You can use a formula text field to display only the most recent value from your append field and then display the formula text field in your reports instead of the append field.

June 2nd, 2009 - 5:06 PM

The simplest way to update a document stored in a file attachment field is to edit the record containing the document, and click on file link next to the file attachment field's entry box.

If you edit a document and want to ensure that no one updates it while you are editing it:

February 5th, 2009 - 6:02 PM

A number of customers have reported that they've deleted file attachments but that this has not reduced the total size of file attachments used by the application.

February 5th, 2009 - 6:02 PM

The reference field (aka record-picker field) in the details table when displayed read-only always displays the value of the key field in the corresponding master record. The key field in the case you cite above is the Record ID#.

February 5th, 2009 - 6:02 PM

The best way to create a user hierarchy in QuickBase is to have a table of users. The key field in this table should be a user field. For each level of the management hiearchy you add another user field to this table. So for example the first user field in this table would be called Sales Rep. If each sales rep has a manager then you would create another user field called Manager.

February 5th, 2009 - 6:02 PM