Salesforce FSC Record Rollup Definitions: How to Roll Up Records to a Household (Step by Step)

This post walks through a hands-on FSC tutorial from FINSforce's YouTube channel, "What Are Record Rollup Definitions? FSC Demo From Scratch", and adds context to reproduce the build and avoid its most common trap. Follow along in your own org, or use this as a written reference.

What is a Record Rollup Definition?

Financial Services Cloud (now branded Agentforce Financial Services) gives admins four ways to roll data up between objects, and it's easy to reach for the wrong one:

• Record Rollup Definition — a standard-object feature, no managed package required, that rolls up related records, such as Cases or Opportunities, from a source object to a target object through a defined join path. This is the subject of this post.
• Rollup Summary / Rollup by Lookup — the more familiar declarative tools for summarizing numeric fields (counts, sums) across a lookup relationship.
• Rollups for managed packages — a separate mechanism pre-built for FSC's own managed-package objects, such as financial accounts and Opportunities rolling up to the party relationship group.
• On-Demand Rollup — less a fourth independent type than a companion capability: the setting and manual "sync now" action that makes a Record Rollup Definition's results appear immediately instead of waiting for the next scheduled run.

Reach for a Record Rollup Definition when you need whole records — a list of Cases, not a sum of dollars — on a related object, using standard configuration rather than a managed package.

The use case: every family member's Cases on the household

The tutorial builds around a common advisor complaint: a household in FSC (an Account record with a household record type) has several family members attached as contacts or person accounts, and each may have raised a support Case. Today, an advisor opening the household can't see those Cases without checking each contact individually.

The fix is a rollup that starts at Case, follows the relationship between a contact and the household, and lands on the household Account, so every Case raised by any family member shows up in one place. To display it, the video drags the Show Record Rollup Results component — a Lightning flexcard — onto the household record page.

The three building blocks: source, target, and the bridge

Every Record Rollup Definition comes down to three decisions, and the video frames them with a driving-directions analogy worth remembering:

• Source object — where you're starting: the records you want to roll up. Here, that's Case.
• Target object — your destination: where the rolled-up records should appear. Here, that's the household Account.
• The bridge (join/filter path) — the turns you take to get there: "go straight, take a left, take a right." Contacts and person accounts connect to households through party-group relationship records, so the bridge here is Account Contact Relation, joined on Account ID on one side and Contact ID on the other.

Getting this right requires understanding the FSC data model — specifically how households, contacts, and party-group relationship objects connect. If that model is fuzzy, the join path will be too.

Build it: step-by-step

1. In Setup, search for Record Rollup Definitions. FSC ships two pre-built definitions out of the box — financial accounts and Opportunities — both targeting the party relationship group, not the household.
2. Click New and name the definition (e.g., "Case on Account Household").
3. Choose the rollup source object — Case — and the target object the rollup should display on — Account.
4. In the builder, click New on the path between source and target and search for the bridge object: Account Contact Relation.
5. Define the bridge connection: Account Contact Relation joins to Account via Account ID, and to Case via Contact ID. The path runs Account ← (Account ID) — Account Contact Relation — (Contact ID) → Case.
6. Add filters if you want — e.g., restricting to Cases where Case Origin = Web. The video's base build skips filters but shows where they'd go.
7. Save the definition, double-checking the join field, then Activate it.
8. On the household's Lightning page, drag the Show Record Rollup Results component onto the page, point it at your new definition, then save and activate the page.

"Activated but nothing shows up?" — the step almost everyone misses

This is the section worth bookmarking. After activating the definition and placing the component, the tutorial hits exactly the wall most admins hit first: the component's Refresh button is disabled, and nothing displays.

The fix is a separate setting. Go back to Record Rollup Definitions in Setup, click Manage On-Demand Rollup, and enable it. Only then does Refresh become clickable — click it, and previously-created Cases appear on the household.

There's a second layer that trips people up even after the rollup works. Once a definition is active and on-demand rollup is enabled, records still sync two ways: scheduled sync via the Data Processing Engine (DPE), running on its own background schedule so a Case created a moment ago won't instantly appear, and on-demand sync via Refresh, the manual "show me right now" action for when an advisor needs to see a just-created Case immediately.

The tutorial demonstrates this directly: after creating a new Case for a second family member, the household doesn't update until Refresh is clicked again. The video defers a full DPE walkthrough to a later episode, so treat scheduling mechanics as a topic to confirm in your own org.

Gotchas worth knowing before you build

• Account can be a target, never a source. You can roll records up to an Account like a household, but not from Account.
• "Contains" isn't literal text-contains. Don't assume the Contains filter operator behaves like a plain substring match — verify it before relying on it for a field like Case Origin.
• Pre-built rollups target the party relationship group, not the household. FSC's out-of-the-box rollups for financial accounts and Opportunities surface on the party relationship group record, a different record from the household. Showing records directly on the household requires your own definition.
• DPE vs. on-demand is a scheduling decision. Decide whether users need real-time visibility (lean on Refresh) or a scheduled cadence is acceptable (lean on DPE), and set advisor expectations accordingly.

What this means for your FSC rollout

Household-level visibility into service activity is a small feature with an outsized effect on adoption. An advisor who has to click into four contact records to answer "has this family had any service issues lately?" will eventually stop asking. A rollup that answers it the moment they open the household gets used every day — and a feature advisors actually open beats a custom report sitting unused in a folder. That's the practical argument for configuring the Record Rollup Definition and its on-demand sync correctly, rather than assuming FSC's pre-built rollups already cover the case. They don't — they target a different object.

If your team is evaluating how this applies to your own FSC data model, household structure, or rollout, Vantage Point can help assess the right configuration and build a practical implementation plan through our Financial Services Cloud services and workflow automation and process optimization work.

Frequently Asked Questions

What's the difference between a Record Rollup Definition and a Rollup Summary or Rollup by Lookup field?

A Rollup Summary or Rollup by Lookup field aggregates a numeric value — a count or sum — across related records. A Record Rollup Definition instead surfaces the related records themselves on a target object, using a join path and a display component like Show Record Rollup Results. Use it when advisors need the actual records, not just a total.

Why is my rollup still blank after I activated the definition?

Activating a Record Rollup Definition doesn't automatically populate results. Enable On-Demand Rollup Definitions (Setup → Record Rollup Definitions → Manage On-Demand Rollup) and click Refresh on the Show Record Rollup Results component. Until on-demand rollup is enabled, Refresh stays disabled and nothing displays.

Can Account ever be a source object in a Record Rollup Definition?

No. Account can be a rollup target — the destination records roll up to — but it can't be chosen as the source object records roll up from.

How often does a Record Rollup Definition actually sync new records?

Depends which path is running. Scheduled runs go through the Data Processing Engine on its own cadence, so a record created moments ago may not appear immediately. If a user needs it right away, the on-demand Refresh action pulls current results instead of waiting for the next scheduled run.

Which object do I use as a bridge to connect records to a household?

For contacts or person accounts, the bridge is Account Contact Relation, joined to Account via Account ID and to the source record (here, Case) via Contact ID. Party-group relationship records generally map people to households in the FSC data model, so understanding that model is a prerequisite for the correct join path.

Do FSC's pre-built rollups (financial accounts, Opportunities) show up on the household or the party relationship group?

They target the party relationship group record, not the household Account directly. If you want related records visible on the household itself, as in this tutorial's Case rollup, you need to build your own Record Rollup Definition targeting the Account.

How do I actually show Record Rollup Definition results on a page?

Drag the Show Record Rollup Results component onto the target record's Lightning page in the page editor, then configure it to point at your definition. Multiple definitions, including FSC's pre-built ones, can be selected from the same component.

Sources

• "What Are Record Rollup Definitions? FSC Demo From Scratch" — FINSforce, YouTube
• Rollup Definitions for Record Rollups — Salesforce Help

Vantage Point is a boutique CRM consulting firm helping businesses transform with Salesforce, HubSpot, and AI — 150+ clients, 400+ engagements, and a 4.71/5 average engagement rating. Learn more at vantagepoint.io.