Roll-Up Summary vs Cross-Object Formula

Aggregate vs Reference: The Core Difference

These two declarative tools are easy to confuse because both cross object boundaries, but they move data in opposite directions. A roll-up summary field lives on the parent and looks down at every related child record, collapsing them into one aggregate value. A cross-object formula lives on a child (or any record) and looks up at one related parent, pulling a single field forward.

Put simply: a roll-up answers “how many, how much, what’s the highest?” across a set of children. A cross-object formula answers “what does the related record say in this one field?” It never aggregates.

Why Roll-Up Summary Needs Master-Detail

A roll-up summary field is only available on the master side of a master-detail relationship — it is not offered on lookup relationships. That constraint exists because master-detail tightly binds child records to their parent (shared ownership, cascade delete, and a required relationship). Salesforce leans on that tight coupling to keep the stored aggregate accurate as children are inserted, updated, and deleted.

The four aggregation types are fixed: COUNT the related records, or SUM, MIN, or MAX a field on them. There is no native average, text, or mode roll-up. You can add filter criteria so only certain children are included — for example, summing Amount only on child records where the stage is Closed Won. Because the aggregate is stored on the parent, it is available to reports, list views, and other formulas without re-querying the children each time. Salesforce’s Trailhead module on roll-up summary fields walks through building one on a master record step by step.

How Cross-Object Formulas Reach the Parent

A cross-object formula uses parent merge fields to walk a relationship path. On a Contact you might write Account.Industry; going further, Contact.Account.Owner.Email. For custom relationships, the relationship name ends in __r — for example Project__r.Status__c. Because the value is calculated when the record is read, it is always current and never occupies stored data.

Salesforce allows a formula to reference fields up to 10 relationships away, and caps each object at a maximum of 10 unique relationships — a limit that is cumulative across all formula fields, rules, and lookup filters on that object. Two formulas on Opportunity that both reach the related Account still count as one unique relationship. Polymorphic fields such as Owner need care, since the owner can be a User or a Queue; Salesforce’s tips for building cross-object formulas document these edge cases and the currency-conversion behavior.

When to Use Which

Reach for a roll-up summary field whenever the answer depends on a set of children: total opportunity value on an account, count of open cases, earliest created date across related records. Reach for a cross-object formula whenever you simply need a parent’s value displayed or evaluated on the current record — the account’s industry on a contact, the parent case’s priority, a related record’s status in a validation rule.

The mechanics of each are covered in depth in the full guide to formula fields in Salesforce, which walks through return types, spanning relationships, and the formula-vs-roll-up decision in more detail. For the aggregation side — the create flow, supported field types, and every limitation — see our companion deep dive on roll-up summary fields.