By Priyanka Kumar
Territory Management grants the users access to accounts, cases, and opportunities which are assigned to the territories. First, a territory hierarchy is created, and then users and accounts are assigned to those territories, as seen here:
In this territory hierarchy, these all are sales territories. The users assigned to US Sales can view all accounts assigned to US Sales and below sales territories. Territory management can be enabled in Enterprise, Unlimited, Performance, and Developer Edition orgs. It can also be enabled by request on Salesforce.com.
Assigning accounts to territories
After creating the territories, you create assignment rules according to which accounts get assigned to each territory. You have the option to manually assign accounts or create assignment rules.
For the assignment rules, you have to specify rule criteria. For example:
Account: BillingCountry equals US
In this case, every account whose billing country is the US gets assigned to the territory for which this assignment rule is created.
Assignment rules limitations and workaround
We have a limitation wherein we can only have up to 10 lines of criteria rules for the assignment rules. In some situations, this is insufficient, like when our criteria exceeds the 10 lines. For example:
If there are roughly 2,000 ZIP codes in one territory and we need to create an assignment rule in which all the accounts which have ZIP codes in these 2,000 ZIP codes are assigned to a territory, this is not possible with a single assignment rule. And we cannot use multiple assignment rules, as they are evaluated as “AND” condition — not as “OR” condition — and all rules must resolve to true.
A way to overcome this limitation is by creating 2 child territories of this territory and assigning the same users to both territories. For instance, suppose Pittsburgh has roughly 2,000 ZIP codes.
In this case, we create 2 child territories — Pittsburgh1 and Pittsburgh2 (keeping their label the same as in the example) — and create a rule for Pittsburgh1 for 1,000 ZIP codes and create a rule for Pittsburgh2 with the remaining 1,000 ZIP codes. And then we assign the same users to both child territories. This way, when rules are run, users within the 2 child territories can see every account that has a ZIP code from the 2,000 ZIP codes.