You are here:
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.
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.
Did this article solve your issue?
Let us know so we can improve!
