When you create an alignment with live data, the alignment requires that you have mapped fields from a data source so that units can appear on the map and be assigned to boundaries. The alignment defines latitude and longitude values, and each boundary set defines other geographic fields. If you’re using multiple boundary sets, each boundary set evaluates the correct fields on your records.
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
Auto-populated Latitude and Longitude Values
If your data source doesn’t specify latitude or longitude fields, the created alignment
queries the underlying source object and auto-populates latitude and longitude
values.
For example, maybe you created a recipe for the Account object in CRM Analytics, but you didn’t include latitude or longitude fields. Territory Planning detects that the recipe is based on the Account object and queries that object for the values.
Although the field values auto-populate, the field itself isn’t visible in the
territory legend unless you add the field to your data source.
Note This functionality isn’t available if your data source is a report.
Matching Strings for Field Names on Boundary Sets
When you create an alignment from live data, geographic fields other than latitude and longitude are mapped to boundary sets. Territory Planning attempts to match field names in this priority order.
First, checks for an exact match, such as BillingLatitude, BillingLongitude, BillingCountry, BillingPostalCode.
Otherwise, checks for a partial match, such as any field that contains latitude or longitude.
Otherwise, leaves the field blank and you have to manually populate it.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
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
Always Active
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
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
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.