PranavNagrecha/AwesomeSalesforceSkills / skills/admin/fsc-relationship-groups
fsc-relationship-groups
VerifiedUse this skill when creating, configuring, or troubleshooting FSC Relationship Groups — including Household, Professional Group, and Trust group types; member role assignment via AccountContactRelation FSC fields; Primary Group designation; and group-level wealth aggregation rollups. NOT for standard account relationships, Contact-Account relationships outside FSC, NPSP household configuration, or Financial Account role setup (use admin/financial-account-setup).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.3 KB |
| references/examples.md | markdown | 8.5 KB |
| references/gotchas.md | markdown | 7.1 KB |
| references/llm-anti-patterns.md | markdown | 10.3 KB |
| references/well-architected.md | markdown | 7.4 KB |
| scripts/check_fsc_relationship_groups.pyexecutable | script | 8.6 KB |
| templates/fsc-relationship-groups-template.md | markdown | 4.1 KB |
references/well-architected.md
View on GitHub# Well-Architected Notes — FSC Relationship Groups
## Relevant Pillars
- **Reliability** — The most significant reliability risk in FSC Relationship Groups is silent data corruption: wealth aggregation rollups that produce incorrect totals without generating errors. Reliable group configuration requires explicit field-setting on every ACR, a custom validation rule to enforce the one-primary-group-per-member constraint, and post-creation rollup validation in sandbox before promoting to production. Batch rollup jobs must be scheduled and monitored to ensure rollup totals are consistent after bulk operations.
- **Operational Excellence** — Group data model changes (switching a member's primary group, adding trust or professional group membership) have downstream effects on wealth dashboards and advisor views that are not immediately visible. Operational runbooks must document the stale rollup window after primary group changes and include a post-change recalculation step. Configuration decisions (which group type, which member is primary) must be recorded in work templates for auditability and handoff.
- **Security** — Relationship Group records inherit standard Salesforce sharing rules. If a Trust or Professional Group Account record is not shared correctly with the advisor or advisor team, group membership and rollup data are invisible to those users even when the underlying financial accounts are accessible. FSC sharing settings (Advisor Access, Branch Access) interact with Relationship Group visibility and must be validated as part of group configuration. Person Account member data is subject to the same privacy and financial data access controls as individual client records.
- **Performance** — Real-time rollup triggers are synchronous and execute in the context of the transaction that creates or modifies a financial account. In bulk data migration scenarios, triggering rollup recalculation synchronously for thousands of financial account inserts can cause CPU time limit exceptions or DML row limit errors. Use the scheduled batch rollup job (`FinServ.RollupBatchJob`) for any bulk load that touches more than a few hundred financial account records.
- **Scalability** — An FSC org with thousands of Household and Trust groups and tens of thousands of ACR records depends on the rollup engine's batch job for consistent aggregation. As group count scales, batch rollup job completion time increases. Monitor batch job execution time and adjust scheduling frequency accordingly. Custom validation rules on ACR (enforcing primary group uniqueness) must be written with governor limits in mind — bulk ACR inserts during data migrations will trigger those rules for every record.
## Architectural Tradeoffs
**Primary Group Designation vs Flexibility.** The one-primary-group-per-member constraint is architecturally intentional: it ensures each client has a single authoritative wealth aggregation unit. This simplifies rollup logic but limits flexibility for clients with genuinely complex multi-group situations (e.g., a client who is equally a primary member of two households post-remarriage). The tradeoff is clean, unambiguous rollup data versus the need for a deliberate primary group designation decision for every multi-group member. Teams that attempt to work around this constraint by setting `FinServ__PrimaryGroup__c = true` on multiple groups produce corrupted data. The correct workaround is to determine which group is the authoritative financial unit and model the other as a secondary relationship container.
**Group Types vs Custom Objects.** FSC provides three group record types (Household, Professional Group, Trust) that cover the most common wealth management relationship structures. Some orgs are tempted to create custom objects for additional group types (e.g., "Foundation" or "Family Office") to avoid adapting to FSC's model. Custom group objects bypass the FSC rollup engine, FSC Lightning components, and FSC relationship panels entirely. The correct approach is to evaluate whether one of the three FSC record types can serve the use case with page layout customization, and only introduce custom solutions when there is a documented platform limitation.
**Real-Time Triggers vs Batch Rollup.** Real-time trigger-based rollups provide immediate consistency for single-record operations but are not designed for bulk data loads. Batch rollup jobs are designed for high-volume recalculation but introduce a lag between data changes and rollup consistency. Production architectures should rely on real-time triggers for day-to-day advisor operations and schedule the batch job nightly (or more frequently for high-volume orgs) to ensure eventual consistency after any bulk operations.
## Anti-Patterns
1. **Using Standard Account Hierarchy (ParentId) Instead of ACR for Group Membership** — Some implementers model FSC group membership by setting `Account.ParentId` on Person Account records to point to a Household Account. This bypasses the ACR junction object entirely, which means `FinServ__PrimaryGroup__c`, `FinServ__Primary__c`, and `FinServ__IncludeInGroup__c` cannot be set. The FSC rollup engine does not listen to the Account hierarchy — it listens to ACR records. No rollup data will populate. Additionally, FSC Lightning components (Household Financial Summary, Group Members panel) rely on ACR-based membership and will not surface members who are linked only via `ParentId`.
2. **Omitting FinServ__IncludeInGroup__c from All ACR Creation Paths** — Teams that build ACR creation through multiple paths (UI Quick Action, Flow, Apex, Data Loader) frequently discover that some paths explicitly set `FinServ__IncludeInGroup__c = true` while others omit it and rely on the default. The result is inconsistent group rollup behavior where some members contribute to group totals and others do not, with no visible distinction in the UI. The architecturally correct approach is to treat `FinServ__IncludeInGroup__c` as a mandatory field in every ACR creation path, not an optional one.
3. **Relying on the FSC UI to Enforce One-Primary-Group-Per-Member** — The FSC standard UI does provide some guardrails when adding a member to a group via the Group Members panel, but programmatic ACR creation (Apex, Data Loader, Flow, external integration) has no such guardrail. Teams that assume the platform enforces uniqueness of `FinServ__PrimaryGroup__c = true` per member discover the problem only when rollup totals become inconsistent in production. A custom validation rule is required.
## Official Sources Used
- FSC Admin Guide: What Is a Group? — https://help.salesforce.com/s/articleView?id=sf.fsc_admin_groups.htm
- FSC Admin Guide: Configure Record Rollups — https://help.salesforce.com/s/articleView?id=sf.fsc_admin_configure_rollups.htm
- FSC Object Reference: AccountContactRelation FSC Fields — https://developer.salesforce.com/docs/atlas.en-us.financial_services_cloud_object_reference.meta/financial_services_cloud_object_reference/sforce_api_objects_accountcontactrelation.htm
- FSC Developer Guide (Spring '26) — https://developer.salesforce.com/docs/atlas.en-us.financial_services_cloud_object_reference.meta/financial_services_cloud_object_reference/fsc_dev_guide.htm
- FSC Trailhead: Create and Manage Household Groups for Financial Planning — https://trailhead.salesforce.com/ (page retired — see host index for current equivalent)
- Salesforce Well-Architected Overview — https://architect.salesforce.com/docs/architect/well-architected/guide/overview.html
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |