Household records and individual-to-household relationships in data loads
Key Takeaway
Load individuals and households first. Then insert each membership as an AccountContactRelation record with IsDirect set to false. On that record, FinServPrimary__c marks the group's primary member, and FinServPrimaryGroup__c marks the individual's primary group.
In Agentforce Financial Services, a household is a type of group that organizes individual clients and gives insight into their household structure. Migrating households takes two loads. First you create the household records. Then you create the relationship records that link each individual to a household. Loading them in the right order, with the right record IDs, keeps every membership pointing at a real individual and a real household.
What a household is in each data model
What makes up a household depends on the data model. Households for Agentic Advisor supports both the managed package and the standard data model.
| Managed package | Standard data model | Households for Agentic Advisor | |
|---|---|---|---|
| What a household is | An Account with the Household record type | A combination of Account and Party Relationship Group records | Account is the primary household object. You can configure Party Relationship Group fields to store extra household information. |
| Inverse relationship records | Auto populated at runtime | Not auto populated | Created automatically when roles and relationships are configured during setup |