Loading

Create a Data Set in Salesforce Maps Territory Planning

Veröffentlichungsdatum: May 29, 2026
Beschreibung
A data set is a copy of the data specified or intended to pull from the source report or the query used. This copy is a point-in-time calculation and won’t reflect changes made in Salesforce after the data set is created. Therefore, any changes made to the data set in the Territory Planning application will not make changes to your Salesforce data and vice versa. You can choose to clone and refresh your data set to re-run any reports or queries to get the latest changes. This allows you to plan based on static and normalized data during your territory carving activity and stage changes until you are ready to commit them back to Salesforce records.

Once the Salesforce object data is imported into the data set, it is referred to as a unit in Territory Planning. A unit can be any Salesforce object with a Latitude and Longitude value.
 
Lösung

Check out the following video to learn how to create a Data set in Maps Territory Planning


To create a data set, review the following:

  1. Click the Territory Planning tab. This will launch the app and bring up the Data Set and Alignment Browser.
    1. If you are already viewing the Territory Planning tab, use the Click To Open link under Data Set at the top left.
  2. Select the Create Data Set button to create a new data set.
  3. Enter a Name and Description (optional) for your data set.
  4. Pick the Territory Boundaries (optional) your alignment will be based on. You can select a single boundary per country, and for certain countries, filter the boundaries. Click Next.
    1. Note: You do not need to wait for filter processing to complete before hitting Next.
  5. Select the report(s) and/or SOQL query or queries that will make up your territory data.
    1. If your report is not already displayed, enter the full report name in the Search Reports box to surface it. Click Next.
      • Note: Reports must be tabular. Matrix, Grouped or Joined reports are not supported.
    2. To create a custom query, use the Build Object Query option.
    3. If a you have Enterprise Territory Management, you can access the Build Territory Model Query from the data set builder to create the queries in order to import your data from ETM.
    4. Note: Data Sets can be made up of combinations of queries and reports. The total number of records cannot exceed 250,000. The records per report cannot exceed 250,000, and the records per query can be more than 250,000 but must be aggregated.
  6. Choose whether or not you want to leverage aggregation to aggregate units to the selected Territory Boundary, meaning a single record will be created for each Territory Boundary with the aggregated numeric values of the units within it. Consider using this option for high-volume unit types or for queries that exceed 250,000 records. There are some key things to remember when using data Aggregation
    1. You will still be able to see the top 10 units per aggregate record from the legend. Units without valid Latitude/Longitudes will be ignored.
    2. After aggregation, non-numeric fields from the data source will no longer be available to display in the legend or include in calculated attributes
    3. Aggregate records take the assignment value of the first unit in the aggregate record
    4. Aggregate records are not affected by “assign nearby containers”, meaning the container assignment and the aggregate record assignment can differ
    5. An aggregate record will be created for every container in a container set
    6. If using multiple reports and aggregating each report, you will get an aggregate type per report.
  7. Configure the data set fields for each selected report. Most of these fields should be populated automatically based on the data source you selected in Step 5.
    1. Unit Name: This field will be leveraged in the legend dropdown and field names.
    2. Unit Id: This field is the unique 15-character Salesforce Id for the Object that you are importing.
    3. Unit Assignment: This field can be leveraged to assign units to pre-existing territories. It must match the Territory Name or Owner at the lowest level of your Territory Model, or else all of your units will be unassigned.
    4. Latitude/Longitude: This field is used to plot units on the map, as well as, assign them to a Territory Boundary if selected.
      1. If the Latitude and Longitude fields are not available in the report, you can use the Import Object Fields option to select those fields
      2. Note: Units without valid Latitude/Longitudes will be ignored.
  8. Confirm the mapping for each and select additional data to include from the Available Fields list.
    1. Important Note: Once you create your Data Set, you won’t be able to modify the reports or fields that have been selected. Meaning, if you need to remove/add a report or include additional fields, you’ll need to recreate the Data Set.
  9. Click Finish.


Cloning a Data Set

  1. From the Data Set's browser, hover over the name of an active data set and click the clone symbol that appears beside the data set name.
  2. Specify if you want to Refresh data sources, which will re-run any reports or queries used to build the data set.
    1. Note: Hover over the data set and select edit to see the data sources associated with the data set.
  3. Specify if you want to Clone specific alignments, which will create a copy of those alignments for associated to the new data set.
    1. Notes: If you select Refresh data sources and Clone specific alignments, then existing units in the alignments will retain their assignments from the alignment and new units will be added to a Newly added units area.
  4. Select Clone to start the process.

Note: If the required fields for building a data set are no longer accessible (i.e., removed from the report, or deleted from Salesforce) then the process will fail. You can see what reports or queries were used to create the data set by selecting edit data set.

 

    Nummer des Knowledge-Artikels

    000389060

     
    Laden
    Salesforce Help | Article