---
schema_version: "1"
id: b3c036769a38cbc6f492ced2911c93748b2ef0d4d3e0b52211f1d2c2b86e7c06
title: Geographic Fields in Live Data Alignments
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/territory_planning_alignments_boundary_geo_fields.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.territory_planning_alignments_boundary_geo_fields.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 86710c47442a6edbcbf3560d0ead50e5437a69eb7ba223e4685f68395e1e2b71
description: 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.
products:
  - Sales Cloud
  - Sales Enablement
release: "264"
---
# Geographic Fields in Live Data Alignments

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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions with <a href="https://help.salesforce.com/s/articleView?id=sales.territory_planning_api_access.htm&amp;type=5&amp;language=en_US" target="_blank">Web Services API enabled</a></td></tr></tbody></table>

## 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 datasets created from SOQL queries only.

For example, maybe you created a query for the Account object in your dataset, but you didn’t include latitude or longitude fields. Territory Planning detects that the query is based on the Account object and queries that object for the values.

![The Setup window for a territory plan, showing the Geographic Fields tab and the auto-populated latitude and longitude values](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_performance_management-264-0-0-production-enus/b1f2feb4-26b8-444f-97f7-be2349869d93/sales_performance_management/images/territory_planning_alignment_geo_fields.png)

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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_performance_management-264-0-0-production-enus/b1f2feb4-26b8-444f-97f7-be2349869d93/images/icon_note.png)

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.