Record rollup definition source, target and join path design
Key Takeaway
A record rollup definition aggregates records from a rollup source object into a rollup target object. When those two objects aren't directly linked, you must add intermediate objects and join fields that build the path between them.
Record rollup definitions aggregate records from different objects so users get a consolidated view of data. For example, a financial advisor can see the financial accounts of all the members of a household. Designing a definition means three choices. You choose the rollup source and target objects, build the join path between them, and add filter conditions that pick the records to include. Then you save and activate the definition.
Rollup Objects
Every record rollup definition needs at least two objects: a rollup source object and a rollup target object. You aggregate records from the rollup source object into the rollup target object.
For a household view, the rollup target object is Party Relationship Group. The rollup source object is the kind of record the household view should gather. Examples are Financial Account for a household's financial accounts, or Case for a household's cases.
These limits apply when you choose the objects:
- You can't select Account as the rollup source object.
- You can't select standard objects that don't have activities enabled as rollup objects. You can select all custom objects as rollup objects.
- You can't use Financial Goal in a record rollup definition, which means you can't roll up financial goals to an account. As a rollup source object, Financial Goal needs Financial Goal Party as an intermediate object to link it to the target object. Financial Goal Party isn't supported.