You are here:
Considerations and Limitations for Branch Management
Here are some things to keep in mind as you implement Branch Management features.

Use more general search terms.
Select fewer filters to broaden your search.
Here are some things to keep in mind as you implement Branch Management features.
| Available in: Lightning Experience |
| Available in: Professional, Enterprise, and Unlimited Editions where Financial Services Cloud is enabled |
If you want to associate branches with underlying accounts, consider creating a record type for those accounts so you can keep them separate from other accounts, like customers and prospects.
There are no limits to the number of Branches or Bankers you can create.
A maximum of 100 branches can be shown in the Branch Selector component.
We recommend that you deactivate branches rather than deleting them if you’re considering closing a branch and reallocating bankers.
The Branch Selector component isn’t certified to work on Mobile.
Branch hierarchies and related service territory hierarchies aren’t automatically synchronized.
The Branch Unit Customer and Branch Unit Related Record objects aren’t available in Related List components.
For each account, you can only create one Branch Unit Customer Record per Branch Unit Record.
We recommend using a developer tool of your choice to mass assign records to Branch Units.
When you merge duplicate accounts that are associated with the same Branch Unit, there can be only one branch unit customer record associated to the duplicate accounts. If more than one branch unit customer record exists, delete branch unit customer records until there’s only one branch unit customer record related to the duplicate accounts.
If you use a custom compact layout for the Branch Unit object, be sure to include the Active and Name fields on the layout so that users can select and update their branch.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.