Skip to main content

​
Overview

Rollup fields aggregate data from related records and display the result as a live field on a parent record. Instead of running reports or manually counting, you can surface numbers like total deal value on an Account or contact count on an Opportunity directly from the record itself. The result behaves like any other field - you can filter on it, sort by it, and reference it in views. Rollup vs. Computed fields If you are not sure which to use:
  • Use a computed field when you want to calculate something using fields on the same record (e.g., a lead score derived from a contact’s title)
  • Use a rollup field when you want to aggregate data across related records (e.g., the sum of all opportunity amounts linked to an account)
See the Computed Fields article for more on that feature.

​
Before You Begin

Only admins can create and manage rollup fields.
  • Rollup fields can be added to Contacts, Accounts, and Opportunities
  • The data pulled into a rollup always comes from one of those three standard object types
  • The data source object type cannot be changed after a rollup field is created - choose carefully

​
Creating a Rollup Field

  1. Go to Settings and select the object you want to add the field to (Contacts, Accounts, or Opportunities)
  2. Scroll to the Custom section and click Add field, then select Create rollup field from the dropdown
Add field dropdown showing Create rollup field option
  1. Enter a Display Name for the field
  2. Optionally add a Description and Help text
  3. Select a Data source object type - the object whose records will be aggregated (e.g., if building a rollup on Accounts, you might pull from Opportunities or Contacts)
  4. Select a Roll-up type - see the Aggregation Types table below
  5. If your roll-up type is anything other than Count, select the Related field to aggregate
  6. Optionally add a Filter in the right panel to narrow which source records are included
  7. Click Create
Reevo begins computing values immediately. The field appears on all records of the target object once the initial calculation completes.

​
Aggregation Types

Roll-up typeCompatible field typesOutput
CountNone requiredNumber - count of related records
SumNumber, Currency, PercentNumber
AverageNumber, Currency, PercentNumber
MinimumNumber, Currency, Percent, Date, TimestampNumber or Date (matches source field type)
MaximumNumber, Currency, Percent, Date, TimestampNumber or Date (matches source field type)
Count does not require a Related field selection. It counts every related record that matches your filter, or all related records if no filter is set. Sum and Average require a numeric field (Number, Currency, or Percent). Minimum and Maximum work on both numeric and date/time fields. The output type matches the source - a Minimum on a Date field returns a Date; a Minimum on a Number field returns a Number.

​
Using Filters

The filter panel on the right side of the rollup field editor lets you narrow which source records contribute to the aggregation. Filters use the same advanced filter interface available throughout Reevo. Examples:
  • On a “Confirmed Deals” count (Account - Opportunities): add a filter for Status = DEAL to count only confirmed deals and exclude prospects
  • On a “Prospects” count (Account - Opportunities): add a filter for Status = PROSPECT to count only early-stage opportunities
Filters can be added, changed, or removed when editing an existing rollup field.

​
Editing and Deleting

​
What you can change after creation

  • Display name
  • Description and help text
  • Roll-up type
  • Filter conditions

​
What is locked after creation

  • Data source object type - e.g., cannot change from Opportunities to Contacts
  • Related field - the specific field being aggregated cannot be swapped

​
How to edit or delete

  1. Go to Settings and select the relevant object (Contacts, Accounts, or Opportunities)
  2. Find the rollup field in the field list
  3. Click the ellipsis (…) next to the field
  4. Select Edit or Delete
Deleting a rollup field removes it from all records permanently and cannot be undone.

​
Examples

​
Opportunity count on an Account

  • Target object: Account
  • Data source: Opportunity
  • Roll-up type: Count
Displays the total number of opportunities linked to each account. Add a filter for Status = DEAL to count only confirmed deals.

​
Total pipeline value on an Account

  • Target object: Account
  • Data source: Opportunity
  • Roll-up type: Sum
  • Related field: Amount
Shows the combined value of all opportunities linked to the account. Add a filter for Status = DEAL to sum only confirmed deals.

​
Contact count on an Account

  • Target object: Account
  • Data source: Contact
  • Roll-up type: Count
Displays the total number of contacts associated with each account.

​
Total deal value on a Contact

  • Target object: Contact
  • Data source: Opportunity
  • Roll-up type: Sum
  • Related field: Amount
Shows the combined value of all opportunities a contact is linked to - useful for understanding individual contributor impact.

​
Troubleshooting / FAQs

Rollup values recalculate automatically when a related record is created, updated, or deleted. Changes to source records trigger an asynchronous recomputation, so there may be a brief delay before the updated value appears on the parent record.
Yes. Once created, a rollup field behaves like any other field. You can use it in list view filters, sort by it, and include it in saved views.
No. The data source object type is locked after creation. If you need a rollup from a different source object, delete the existing field and create a new one.
No. Rollup fields cannot currently be referenced inside computed field formulas. They are independent field types.
A blank value usually means the record has no related records of the source type, or all related records were excluded by your filter. A zero value for Count means zero matching records exist. Check your filter conditions and confirm that records of the source type are actually linked to the parent record.
Rollup fields on Custom Objects are not yet available for all workspaces. This article covers rollup fields on the three standard CRM object types: Contacts, Accounts, and Opportunities.
Computed fields calculate values using fields on the same record - for example, a score derived from a contact’s job title. They cannot pull data from related records. Rollup fields aggregate data across related records - for example, the total value of all opportunities linked to an account. Use a rollup when the data lives on a different object type.
Yes. Because rollup fields are stored like any other field value, you can use them as trigger conditions or filter criteria in workflows.