Salesforce Docs Portal

Considerations, Allocations, and Guidelines for Planning Territories with Live Data

Prepare for planning territories with live Salesforce data and discover how it differs from copied data when you create datasets in Territory Planning.

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
Goal Details about Using Live Data
Create and work with datasets and alignments Whoever creates and works with live datasets and their alignments require access to all referenced fields within those datasets and alignments.
Add data sources to datasets

Allocations and supported functions differ from copied data. Here’s how.

  • Each report can include up to 50,000 records.
  • Each query and segment can include up to 100,000 records.
  • Each dataset can include up to 100,000 records.
  • Territory models from Sales Territories aren’t available as a query data source.
  • Aggregation for reports, queries, and segments isn’t available.
  • You can add unit attributes, but can’t update existing unit attributes.
Plan territories on the map

Map requirements and functions differ from copied data.

  • Include latitude and longitude coordinates as attributes.
  • If you plan territories with boundaries, set the postal code boundary type. Assignments rely on postal and country codes, instead of latitude and longitude coordinates.
  • Specify up to five boundary sets per alignment.
  • Live datasets don’t support using the analyze and compare function with non-geographic datasets.
Optimize performance when loading alignments

The number of attributes you include and how you handle unassigned units affects performance.

  • Alignments can include up to 20 attributes at a time with the option to exchange them for others.
  • Alignments can require more time to load when you exclude unassigned units in alignments.
Publish territory plans Publishing alignments to Sales Territories and CSV files doesn’t include point ZIP codes.