1. Scenario Example

Payment Collection detail records lookup to Sales Order. Create a reference field on the Payment Collection detail object that references fields on the Sales Order.

2. Configuration Notes

• Supports cross-object data retrieval: in a one-to-many relationship, the “many” side can display a field value from the “one” side.

3. Common Questions about Reference Fields

3.1 Difference between reference fields and default values

A reference field reflects changes in the referenced field value. A default value does not change after being set.

3.2 Which field types can reference be used with

Currently supported referenced field types: single-line text (except owner’s primary Dept.), multi-line text, single select, multi-select, number, currency, date, time, datetime, mobile, email, boolean, percent, URL, location, country, state/province, city, district, township, village, auto-number, user, Lookup (lookup relationship), Master-Detail (master–detail relationship), Departments, Images, Record Type.

(Note: standard CRM terms used where applicable: Lookup, Master-Detail, Departments, Images, Record Type.)

3.3 Timeliness of reference fields

3.3.1 Are reference fields updated in real time?

Reference fields that do not support filtering are calculated in real time when querying data. Reference fields that support filtering are calculated asynchronously by background queues, not in real time, so there can be delays. Delay duration depends on the number of queued tasks. Tenants with a dedicated database receive a separate compute queue.

3.3.2 Timeliness when computing for many records

1. When a reference field is newly created or reconfigured, it will recalculate historical records. For large datasets, this recalculation can take a long time.
2. Bulk imports or bulk updates via buttons also trigger incremental recalculation, which may be delayed.

3.3.3 Timeliness when computing for a single record

When the referenced field on the source record is edited, the reference field begins recalculation for that record.

3.4 Why reference fields may not support filtering on list views (see Figure 3.4)

1. A reference field can be filtered on list views only if the field configuration has “support filtering” enabled.
2. Reference fields that reference Lookup, Dept., User, or Images fields do not support filtering (when selecting these source field types, the “support filtering on list view” option becomes disabled).
3. If you add a reference field and enable filtering, immediate filtering on the list may still fail because field values must be calculated before filtering is possible. If calculation hasn’t completed, filter results may be incorrect.
4. Reference fields that do not support filtering cannot be used as filter conditions inside functions.

Figure 3.4 — Field configuration: whether the reference field supports filtering

3.5 Can reference fields be aggregated on list views?

Reference fields cannot be aggregated on list views. This applies to all reference field types, including those that support filtering.

3.6 Can reference fields be used in calculations or statistics?

Calculated fields, roll-up/statistic fields, and default value formulas cannot reference reference fields for calculation or aggregation.

3.7 Can reference fields point to calculated fields?

Reference fields cannot reference calculated fields. They also cannot reference roll-up/statistic fields or other reference fields.
Recommended approach: use a calculated field, and in the calculation formula’s Advanced Mode reference a calculated field on the related object.

3.8 Can reference fields trigger UI functions?

Reference fields cannot trigger UI events.

3.9 List view shows values for a reference field but filtering does not return records

Because reference field calculation can be delayed, users often encounter cases where list view displays a value but filtering by that value returns no results. If you see a field value on the page but cannot filter by it, first consider whether the field is a reference field.

Reason: the list view displays reference field values that are calculated when the list is loaded. Filtering uses values stored in the database. If the reference field’s calculation result has not yet been written to the database, filter results will not match the displayed list.

• If you recently created the reference field, changed its “support filtering” setting, or bulk-modified referenced data, please wait until the reference field calculation completes.
• If your reference field consistently filters incorrectly for a small subset of records and there is no ongoing calculation, report the issue for investigation.