To help you maintain and improve your apps, you can check field usage information including:
- Pipeline name - a clickable URL that opens the associated pipeline where the field is used
- Owner - the name of the pipeline owner
- Reason - the indexes of the steps within the pipeline where the field is used
Field usage and count don't show if:
- A field is used in steps through Jinja expressions
- A sub-field is exclusively used in the advanced query field
- A sub-field is used in the following steps: Import with CSV, Remove Record(s), Copy Records, and Export Records to CSV
To check field usage:
-
Select the table that contains the field.
-
Select Settings, then choose Fields.
-
Hover over the field name, then select Where is this field used? in the dialog box that appears. The Usage page displays a list of the places where the field is used in your app.
Alternatively, if you are editing a field's properties, select the Usage tab.
Types of field usage information
The table on the form usage tab displays the following types of field usage information if relevant.
Forms and reports usage
- Form-based access permissions
- A form rule, with information on which form rule
- Exact forms or an advanced dashboard
- A report link
- Report formulas
- Row color-coding for reports
- Initial filters for reports
- Default report settings
- All reports that use the default report settings are italicized with a note that they use the default fields. This way, if you need to delete or change a field, you can easily see if the field is part of the default settings and only change the report settings once.
Derived fields usage
- Lookup fields
- Summary fields
- Formula fields
- A snapshot or shared values field
Other
- Used in an email reminder or notification
- Used in a webhook
- Part of a table-to-table relationship
- Used in a custom data rule
- The number of records that have a value in this field with a link to a table report of those records
- Estimated space (memory or data) consumed
Due to variations in how Quickbase and data are used, we provide an estimated size for each field to provide a sense of relative field usage. This value may also change as an application is used.- For scalar (data entry) fields, this represents the total size of the field as stored on disk. For derived fields (summary, lookup, formula), this represents memory since these values are not stored.
Address fields
For address fields, also known as composite fields, field usage info reflects both the primary field and all of its sub-fields. For example, if users enter Street 1, City, State/Region, and Postal Code separately, the record will be counted in the total number of Address field records. Also the memory used by all these sub-fields will be counted in the memory usage total for the Address field. The exception is when the Country field has the default value “United States,” then the Country value is not counted.
In pipelines, there are specific limitations for displaying sub-field usage. Field usage information isn't shown and counts aren't changed in the following cases:
- When the sub-field is exclusively used in the advanced query field
- When the sub-field is used in the following steps: Import with CSV, Remove Record(s), Copy Records, and Export Records to CSV
Dependency diagrams
You can use field dependency diagrams to help you better manage and track your apps by tracing the source of your fields. Field types that show a dependency diagram include:
- Address
- Lookup
- Summary
- Formula
- Composite fields used in Quickbase Sync
- Fields referenced in the filter criteria of a Summary field
To view the interactive diagram, select one of these field types in a field list and click the Dependency diagram tab. Select the circle next to a field name to view the fields it includes.
When it's applicable, the table the field is used in is also displayed. You can drag the diagram to recenter it and use your browser controls to zoom in and out. Dependency diagrams include red and blue nodes. Select blue nodes to expand them. You can't expand red nodes.