Published at: 2026-09-17
Roll-up summary field
Overview
The Roll-Up Summary Field aggregates field values from detail objects or lookup-related objects and stores the result as a field value on the current object. It applies to cross-object aggregation scenarios such as total order amount and customer contact count. Supported aggregation operations include sum, count, max, min, and average.
Use case
In many business scenarios, you need to aggregate field values from detail objects and lookup-related objects and use the result as a field value on the current object. For example, the total order amount is the sum of the price field values from all order detail records.
Roll-Up Summary Fields support creation on the master object in a Master-Detail Relationship. You can perform aggregation operations on the detail object or related object itself or on a specific field.
Configuration guidelines
Target aggregation object
You can select detail objects or related objects.
Aggregation type
| Type | Description | Example |
|---|---|---|
| COUNT | Counts the number of records | Number of contacts under a customer |
| SUM | Sums a specific field | Total product amount under a sales order |
| MAX | Returns the maximum value of a specific field | Largest opportunity amount under a customer |
| MIN | Returns the minimum value of a specific field | Lowest sales expense under a customer |
| AVG | Returns the average value of a specific field | Average product discount across order products |
Field aggregation
If the target aggregation object has fields that support the selected aggregation type, you can configure field aggregation by selecting the target field.
Rounding rules
- Round up: Increments the last retained decimal place by 1.
- Round down: Truncates digits beyond the retained decimal places.
Example:
2.124 with 2 decimal places — round up produces 2.13, round down produces 2.12.Filter conditions
- Fields referenced by aggregation filter conditions cannot be disabled.
- Changing filter conditions requires the system to recalculate all data. Avoid frequent modifications.
Field types supported as roll-up summary filter conditions: Text, numeric, single-select/multi-select/Boolean, Personnel/Personnel (Multi-Select), Department/Department (Multi-Select), Lookup Relationship, Country/Province/City/District, Location.
Unsupported field types:
- Formula: Not supported regardless of whether the formula field is filterable.
- Roll-Up Summary Field.
- Reference Field: Not supported regardless of whether the reference field is filterable.
- Component fields: Payment (Collection) component, Check-in component, Area location, Date range.
- Business fields: Star rating, Video, Appointment time slot.
- Other unsupported fields: Lookup Relationship (Multi-Select), Rich text, Collaborative rich text, Long text, Image, Attachment, External personnel, Related business data, Related business object, and so on.
Default value and required settings
Default value
Roll-Up Summary Fields do not support default values. The system calculates the value automatically based on the aggregation rules.
Required settings
- Field-level required: Set “Required” to “Yes” on the field configuration page. This applies across all scenarios (front-end entry and back-end import). The system blocks saving if the field is empty.
- Layout-level required: If the field is required only in specific business scenarios, set it as not required in the field properties, and then select “Required” in the specific page layout editor.
- Conditional required: If the required condition depends on the value of another field, configure validation rules.
Historical data calculation on save
When you click Save on the field edit page and the data volume exceeds 100,000 records, the system displays a prompt:
| Option | Description |
|---|---|
| Do not calculate existing data | Does not recalculate historical data created before the roll-up summary field was added |
| Calculate all | Recalculates all existing data for this object (for large data volumes, roll-up summary field values may be empty for a period) |
| Calculate data matching the following scope | Configure conditions as needed; only data that meets the conditions is calculated |
When the data volume is 100,000 or fewer records, no prompt appears and the system saves normally.
[!WARNING] - When some fields under the roll-up summary field are not accessible to the current role, the roll-up summary field does not calculate or returns an empty result. - Aggregation on related objects is calculated asynchronously. Results may be delayed.
View aggregation task progress
After you create or edit a roll-up summary field, calculating historical data may take a while. The system provides a progress tracking entry. When a task is running or waiting, you can view the aggregation task status. The list displays a Calculation task status button. Click it to view the task status, total data volume, completed data volume, and estimated completion time.
Troubleshooting
Roll-Up summary field has no value or incorrect value
Scenario example:
The Order Amount (Original Currency) field on the Order object is a roll-up summary field that sums the Price values from all products in the Order Product detail object.
Screenshot missing: Roll-Up Summary field configuration details.
However, the Order Amount (Original Currency) field shows no value on the list page.
Calculation delay causing empty roll-up summary field
- Confirm whether the roll-up summary field was recently created or re-edited. In this case, the field recalculates historical data. For large data volumes, the delay can be significant. Wait several hours or a day before checking.
- Bulk imports or button-triggered batch updates also cause incremental aggregation delays.
Roll-Up summary field configuration error
- Target aggregation object is incorrect: You intended to aggregate Object A but configured Object B. Verify the Target aggregation object setting first. (This check applies only to related objects, not detail objects.)
- Field aggregation is incorrect: If the target aggregation object is correct, verify that the aggregated field actually contains data.
- Filter condition is incorrect: Verify that the data scope filter conditions are correct.
Method 1: Filter data on the aggregated object. Identify the lookup field and the specific record whose aggregated value is incorrect.
Method 2: Open the detail page of the record with the incorrect value. Check the related list of the aggregated object for data.
Method 3: Verify the filter conditions configured for the aggregated data.
Value overwritten by function
The roll-up summary calculation service produces correct results, but subsequent concurrent updates from workflows or UI functions may overwrite the value. Check the modification history. If post-action functions or UI functions are configured after record creation/editing, update the function to use incremental updates:
// Full update (may overwrite other fields)
Fx.object.batchUpdate(<apiName>, <objects>)
// Incremental update (recommended; fields parameter specifies the field list)
Fx.object.batchUpdate(<apiName>, <objects>, <fields>)
Lookup aggregation field configuration error
Re-examine the roll-up summary field configuration to confirm which lookup relationship field on the aggregated object establishes the aggregation relationship. Common misunderstanding scenarios:
- A roll-up summary field on the Account object counts sales records. The roll-up summary uses a standard lookup field on the Sales Record object, but some sales records do not have this lookup field filled in — they only associate the customer through the “Related business data” field.
- A roll-up summary field on the Personnel object counts how many customers a person has. The roll-up summary should use the Lookup Relationship (Personnel) field on the Account object, not the Owner field on customer records.
Roll-Up summary field configuration notes (related objects)
In the dropdown list, you may see parenthetical information after the object name. This occurs when an object has two lookup fields referencing the same target object. When configuring a roll-up summary field, confirm which lookup field to use for the aggregation. The parenthetical text is the related list page title of the lookup field.
If the roll-up summary target is a specific lookup field, only records with a value in that lookup field are included in the aggregation. To verify from the related object detail page, confirm that the corresponding related list contains data.
How to aggregate other field content with a roll-up summary field
First select the target aggregation object and aggregation type. If the target object has fields that support the selected type, a field aggregation option appears. If no supporting fields exist, the option is not available. After selecting the target object and type, choose the field from the field aggregation dropdown.
Roll-Up summary field timeliness
- Roll-Up Summary Fields do not update in real time: They calculate asynchronously in the back-end queue. Some delay exists, depending on the number of queued tasks. Tenants with a dedicated database receive a dedicated calculation queue.
- Multiple records: If the roll-up summary field is newly created or re-edited, historical data is recalculated. For large data volumes, the delay can be significant. Bulk imports or button-triggered batch updates also cause incremental aggregation delays.
- Single record: The roll-up summary field begins calculating after the aggregated object data is submitted (creation or edit completed).
- Last modified time: When only roll-up summary field, reference field, or formula field values change and no other field values change, the record’s last modified time does not update.
Discrepancy between roll-up summary field and layout summary
Roll-Up Summary Fields sum values directly from the database. The list page sums values after formatting decimals. If the database stores extra decimal places, the two totals may differ.
Example: An Amount field is configured to 2 decimal places. A roll-up summary field aggregates it with 2 decimal places. The list page also summarizes the amounts.
List summary (round first, then sum):
| Original value | Rounded |
|---|---|
| 7580.94679 | 7580.95 |
| 3925.088338 | 3925.09 |
| 51323.718268 | 51323.72 |
| 58677.945154 | 58677.95 |
| 20192.24145 | 20192.24 |
| Total | 141699.95 |
Roll-Up Summary Field (sum first, then round):
Raw sum:
7580.94679 + 3925.088338 + 51323.718268 + 58677.945154 + 20192.24145 = 141699.94| Method | Result |
|---|---|
| Round first, then sum (List summary) | 141699.95 |
| Sum first, then round (Roll-Up Summary) | 141699.94 |
Decimal place configuration notes
- Functions can write numbers with more decimal places than configured. Even if 2 decimal places are configured, the actual value may have 3 or 4 decimal places. Format decimal places before writing values through functions.
- Decimal place restrictions apply only to page input. If a function populates a value that exceeds the decimal place limit, the Web client does not block submission, but the mobile client does.
- When a numeric field’s actual decimal places exceed the configured count, the page still displays the configured number of decimal places.
Excel total vs roll-up summary field discrepancy
When you export list page data and calculate totals in Excel, the result may differ from the roll-up summary field value. Consider whether to round first then sum, or sum first then round. If the Excel field is calculated by an Excel formula, try adjusting to more decimal places first to observe the effect.