--- schema_version: "1" id: 4f9942dc36e22c372513e8372b9a1b9b3daa35d340f9c7cc40ded50895f234dd title: Considerations for Planning Territories with Copied Data collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/territory_planning_data_sets_static_data_considerations.md canonical_url: https://help.salesforce.com/s/articleView?id=sales.territory_planning_data_sets_static_data_considerations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: b438f794c6d698e6aa7f751318b85dd5782ab40eb2be3826861ac37a004c7cb0 description: Prepare for planning territories with copied Salesforce data when you create datasets in Territory Planning. products: - Sales Cloud - Sales Enablement release: "264" --- # Considerations for Planning Territories with Copied Data Prepare for planning territories with copied Salesforce 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
## Methods for Creating Datasets with Copied Data You choose a method for creating your datasets using Salesforce reports, SOQL queries, Sales Planning segments, or a combination of them all. Supplement that data with attributes from external sources in CSV files.
If you import... Select any combo of... Here’s Why
As many as 250,000 records Salesforce reports and SOQL queries Reports can include as many as 250,000 records. It’s fine for you to select multiple reports when you create datasets as long as they collectively contain no more than the 250,000 record allocation for each dataset.
More than 250,000 records Salesforce reports and SOQL queries, and the option to aggregate records

If you plan to import high volumes of data, it’s best to turn on the Bulk API setting and select SOQL queries as your data sources. That way you speed up the import process and reduce the likelihood of you encountering Salesforce governor limits. In addition, if you aggregate records within territory boundaries, you can:

  • Include more records in your datasets that otherwise exceed the 250,000 record allocation.
  • Get a simplified view of the units as a single unit within each boundary on the map.

When you aggregate records, keep in mind that:

  • Units within a boundary appear as a single aggregated unit.
  • Assignments for aggregated units adopt the assignment value from one of the units within that boundary.
  • Numeric values for aggregated units represent the sum of all units within them.
## Fields to Include for Importing the Right Data Include these essential fields in the datasets that you create.
Field or Field Type It’s good to know that...
Record Id Territory Planning requires 15-character record IDs for every record you import.
Latitude Territory Planning requires latitude and longitude data and skips importing records without it.
Longitude
Assignment Typically, assignments come in the form of a territory name, username, or user ID. If your company includes large teams—with some teammates who share first and last names—user IDs eliminate any potential for confusion.
Descriptive fields Descriptive fields help with searching, filtering, and exporting. For example, add fields such as Account Name, City, State, Market Segment, and External Id.
Numeric fields Numeric fields help with aggregating data at the territory level or optimizing alignments. For example, add fields such as Annual Revenue, Employees, and Potential.
## Attributes from External Sources When you create datasets, you can add supplemental, external data in CSV files. Your supplemental data can include attributes that: - Get your territory models further dialed-in by appending fields that include relevant data stored outside Salesforce. - You want to adjust and include as model data that you later export to proprietary and third-party systems. ## Guidelines and Considerations for Optimizing Performance The amount of data that you include in datasets can affect how they build and the speed at which their alignments load. - Even though you’re unlimited in terms of the fields you include in datasets, performance is at its best when you include up to 25 fields. - Consider that the number of fields, their types, the number of records, and their contents can affect performance. For example, long text area fields can impact performance more than numeric fields.