Loading

Data Flow in Salesforce Maps Territory Planning

Fecha de publicación: Aug 4, 2023
Descripción
A Simplified flow of data in Salesforce Maps Territory Planning can be represented as below:

Define your Salesforce Report or SOQL query criteria --> Create a data set --> Create alignments --> Publish
Solución

Import data

To import data into the application, you can use a single or multiple Salesforce reports, SOQL query or a combination of both. The data pulled from these sources is then imported as a data set into Territory Planning. 

Note: The Salesforce report or SOQL query being used to import data should contain the Salesforce Object Id, Latitude and Longitude values at a minimum.
 

Create a data set

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 doesn’t link back to the original report or SOQL query. Therefore, any changes made to the data set in the Territory Planning application will not make changes to your Salesforce data or vice versa. This allows you to plan based on static data during your territory carving activity. You can utilize the Clone and Refresh feature to create a copy of your data set and re-run the reports or queries to return the latest data in a new data set.
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.


Create an alignment

Once the data set is created, you can then create an alignment. An alignment is a map-based visualization tool used for planning different scenarios and adjusting the assignment values of your unit data without impacting the Salesforce data. Data sets can have multiple alignments, which are different planning scenarios. You can use the alignments for planning and invite other users to provide feedback if necessary before committing alignment changes back to Salesforce. Alignments must be published before they can update any Salesforce data.

Note: You can also enrich your data with external attribute data (CSV file). However, external attributes can only enrich existing Salesforce records and cannot add new records. Although this can be done either during data set creation or while working in an existing alignment, it is best practice to import external attributes when creating the data set. This ensures the data gets carried to all alignments associated with the data set. 


Publish data

Once your planning activities are complete, you can then publish assignment changes using the five publishing options: Enterprise Territory Management, Salesforce Maps Shape Layers and Auto Assignment Rules, Salesforce Fields, PDF handout, and/or a CSV.

When publishing to Salesforce Maps, the territories will be published in the form of shape layers which can be linked to auto assignment rules in Salesforce Maps Settings. These assignment rules can be generated automatically from Territory Planning and will associate the corresponding shape layer with the Territory Owner. These rules can then point to specific Salesforce objects and update user lookup values such as OwnerId.

When publishing to ETM, you can publish territories, users, manually assigned accounts, and geographic assignment rules. Your territory owner and any additional users will be assigned to the corresponding territory. You can create geographic assignment rules based on the Territory Boundary selected during the data set creation process, such as United States Postal Codes. Locked units can also be published as manually assigned accounts.

When publishing to FSL, you have the ability to publish your alignment directly to the Field Service managed package as Service Territories and Service Territory Polygons.Publish to FSL only publishes Service Territories and Service Territory Polygons. This option will only appear for Orgs that have Field Service enabled, and the managed package installed.

When publishing to Salesforce Fields, you can write the Territory Planning object and field values directly over to fields found within Salesforce records such as, Accounts, Opportunities, Leads, and even Custom Objects. This will enable users to operationalize their territory designs without needing to utilize an intermediary tool such as Enterprise Territory Management or Salesforce Maps.

When publishing to CSV, you can quickly create extracts of the entire focus or alignment without needing to select anything on the map.

You can also leverage Export to CSV to extract selected information at any level of your legend, which can be used to update external systems.

Note: Publish to CSV is introduced in the Winter ’22.
 
Número del artículo de conocimiento

000389035

 
Cargando
Salesforce Help | Article