Loading
Sales Performance Management
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Boundary Matching Requirements in Live Data Alignments

          Boundary Matching Requirements in Live Data Alignments

          When you create an alignment with live data, Territory Planning tries to match the country and postal code string values in your data source with your boundary set definitions.

          Required Editions

          Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
          Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions with Web Services API enabled

          Territory Planning attempts to match values in this priority order.

          • First, checks for an exact match of both country code and postal code, such as USA and 94105.
          • Next, checks for an exact match on the countrycode_zipcode key format.
          • Next, checks for an exact match on the postal code only. If two postal codes are matched because the alignment has multiple boundary sets, a postal code value isn’t assigned.
          • Next, checks for matching point ZIP codes.

          For postal codes, only the important digits for your territory plan are evaluated. For example, if you plan limits US postal codes to five digits but your data source uses a nine-digit US postal code such as 12345-6789, only the first five digits 12345 are evaluated.

           
          Loading
          Salesforce Help | Article