Financial Services Cloud Availability and Limitations
Financial Services Cloud works differently from other Salesforce features. Learn about the issues to expect as you implement the app and as your users start to work in it.
Required Editions
| Available in: Lightning Experience |
| Available in: Professional, Enterprise, and Unlimited Editions |
Important Financial Services Cloud objects such as Financial Account, Financial
Account Role, and Assets and Liabilities support up to 70 million records at rest. Data Loader is
supported for loads of up to 5 million records. Rollup summary calculations support a load volume
of 5 million Financial Account records.
To support or load records above these limits, we recommend you work with a Salesforce partner. Or visit AppExchange for a suitable data load partner product. The number of records you can import depends on your permissions and the type of data you’re importing. You can import as many records as allowed, as long as you don’t exceed the overall data storage limits for your org.
Supported Browsers
Financial Services Cloud is available in any of the Supported Browsers for Lightning Experience.
General Sales Cloud and Service Cloud Compatibility
The Financial Services Cloud documentation describes the Sales Cloud and Service Cloud functionality with which the Financial Services Cloud features work. Salesforce makes no representation regarding Financial Services Cloud features functioning with any other Sales Cloud and Service Cloud functionality not expressly stated in the Financial Services Cloud documentation.
Features Not Supported with Financial Services Cloud
- Accessibility features aren’t incorporated.
- Shared Activities aren’t supported in group rollup summaries.
General Limitations
Note These limitations apply to person accounts and the individual object model.
- The number of Financial Account records that you can associate with an account record is limited. Exceeding the number of Financial Account records can cause a query row governor limit error.
- When users create or edit group memberships, group rollup summaries are updated, except when a person is made a member of multiple groups. Group rollup summary data is reflected only for the primary group.
- Lead conversion isn’t supported for Group record types, including the Household account record type.
- When multiple currencies setting is enabled, note these limitations:
- Financial Services Cloud packaged components don’t display record-specific multiple currency settings. Only the user-specific currency settings are displayed. The Currency Iso Code field doesn’t change currency symbols in packaged components.
- Advanced currency management isn’t available.
- The Currency Iso Code field must be included on page layouts that have a currency field.
- When filtering by currency values in reports or list views, users must specify a currency ISO code, such as USD or GBP, before the value. For example, GBP100000. The ISO code must be one of your org’s active currencies.
- When Multiple Currencies and Rollup By Lookup are both turned on in an org, the currency
summary fields on the Account record are reset to the default org currency.
- To accurately calculate the total financial account value of an Account record, user currency and account currency must match the org default currency.
- To show commas and symbols correctly on the Financial Account Summary component, a user’s locale in Locale Settings and the user’s currency must match.
- Localization in Danish, Dutch, French, German, Italian, Japanese, Portuguese (Brazil),
Swedish, Hebrew, and Spanish are provided, with the following exceptions.
- The names of the packaged Advisor, Personal Banker, Relationship Manager, and Client Associate profiles are in English.
- Financial Services Cloud custom tab labels on the individual and group profile pages are in English. To change tab labels on the profile pages, edit the labels from a custom client record page in the Lightning App Builder.
- Events that are set to repeat by using the IsRecurrence2 field on the event record are excluded from Financial Services Cloud group record rollups. As a result, even if group rollup is enabled and rollups for events or activities is enabled, the FinServ__Household__c field value on these events isn’t set by rollup. Also these repeat events aren’t included in component record lists such as the Household (Account) Activities related list.
- Activity rollup fields to a group aren’t supported when Allow Users to Relate Multiple Contacts to Tasks and Events is enabled.
- Rollup summary fields aren't available in a Partial Copy sandbox. To use roll-up summary fields in a Partial Copy sandbox, create a Full sandbox or install the Financial Services Cloud managed package in a Partial Copy sandbox.
- When you create a CCR or AAR record using the external ID, Salesforce creates an inverse CCR or AAR record and appends "_inverse" to the inverse record’s external id. External IDs can be a maximum of 56 characters.
- If you deactivate an Account Contact Relationship between a business and an individual, you can’t create an Account Contact Relationship between them. Instead, reactivate the original Account Contact Relationship.
- Financial Services Cloud installation isn’t supported on an org with a previously installed version of the Wealth Management app.
- Financial Services Cloud custom components aren’t fully supported in the Salesforce mobile app.
- The flows in Financial Services Cloud are available only in English.
- Each Financial Account must have at least one active Financial Account Role of the type Primary Owner, or data loading errors can occur.
- Duplicate Management isn’t fully supported. Detection and prevention are supported; record merge isn’t supported.
- The UI components in Financial Services Cloud managed package are built with Aura and don't fully support Lightning features like Dynamic Forms. We recommend that you use the standard UI components whenever possible for optimal functionality. For example, Relationship Map is built with Aura and Actionable Relationship Center is a standard UI component.
- Review the Requirements to Populate the Financial Services Cloud Managed Package Birthday Card Component.
- When you delete the criteria for Record Association Builder, the system also purges any related branch unit records. The purging happens because the association criteria act as a foreign key on the Branch Unit Related Record object, triggering a cascade deletion of branch unit related records when the criteria are removed.
Person Account for Financial Services Cloud Limitations
- The Create Individual - Financial Services Cloud component (the Client Profile Builder) isn’t supported.
- Person accounts are displayed as contacts in the Salesforce Inbox sidebar.
- Creating a client record via Salesforce Inbox isn’t supported.
Individual Data Model Limitations
- To follow an individual, make sure that you explicitly follow the individual's account and contact records. To follow both account and contact records automatically, contact your Salesforce representative.
- In Financial Services Cloud, the unified object view of an individual relies on the Contact redirect. In the Retail Banking Console, this redirect might be disabled in your org.
- When you create an individual account, the name fields on Account and Contact are synchronized. Financial Services Cloud account names don't include salutations, middle names, or suffixes. For example, Dr. John Michael Smith Jr. appears as John Smith.
- Access to individual and group profiles on the Salesforce mobile app isn’t fully supported. For more information, see Modify the Mobile Navigation Menu.
- Deleting an individual via Salesforce Inbox isn’t supported.
- Creating a client record via Salesforce Inbox isn’t supported.
- Considerations for Converting Leads in Financial Services Cloud.
Client Segmentation App Limitations
A CRM Analytics Growth, CRM Analytics Plus, or CRM Analytics for Financial Services license is required to access full CRM Analytics capabilities.
| Capability | CRM Analytics Growth or Plus; CRM Analytics for Financial Services | Client Segmentation App |
|---|---|---|
| Data sources | Salesforce and external data | Salesforce data |
| Object support | Standard and custom objects | Standard and custom objects |
| Data volume |
|
10 million rows |
| Customize existing dashboards? | Yes | No |
| Create dashboards? | Yes | No |
| Customize existing datasets? | Yes | No |
| Create datasets? | Yes | No |
| Create custom CRM Analytics apps? | Yes | No |
| Supports Einstein Discovery and Experience Cloud integration? | Yes | No |
| Supports bulk actions and APEX steps? | Yes | No |
| Supports Sales Cloud Einstein AI? | No | No |
| Supports Salesforce Inbox? | No | No |
CRM Analytics for Financial Services gives you the same access to CRM Analytics capabilities as the CRM Analytics Growth and Plus licenses. Consult this chart to see any limitations.
| Capability | CRM Analytics Growth or Plus; CRM Analytics for Financial Services |
|---|---|
| Data sources | Salesforce and external data |
| Object support | Standard and custom objects |
| Data volume |
|
| Customize existing dashboards? | Yes |
| Create dashboards? | Yes |
| Customize existing datasets? | Yes |
| Create datasets? | Yes |
| Create custom CRM Analytics apps? | Yes |
| Supports Einstein Discovery and Experience Cloud integration? | Yes |
| Supports bulk actions and APEX steps? | Yes |
| Supports Sales Cloud Einstein AI? | No |
| Supports Salesforce Inbox? | No |
Experience Cloud Site Limitations
- Partner Community, Customer Community Plus (CCP), or Customer Community licenses are required. Experience Cloud license restrictions and limitations apply.
- For advanced sharing, such as sharing financial account records across multiple owners, Partner Community or CCP licenses are required.
- Manual provisioning must be completed in Salesforce Classic.
- In Financial Services Cloud, if the org enforces private sharing on accounts and contacts, guest self-registration fails when the account owner is changed.
- Other provisioning methods aren’t supported.
- Financial Services Cloud components aren’t compatible with Lightning Out.
- Task queues aren’t supported in Experience Builder pages.
Did this article solve your issue?
Let us know so we can improve!
