Routes is the feature that supports the use of Custom Drive Profiles. Custom Drive Profiles are used to create routes that are optimized for trucks and other vehicles that might not be able to travel the same roads as passenger cars3. A route can be optimized based on the specificcharacteristics of a truck and its cargo, such as height, weight, length, and hazardous materials3. To use this feature, the user needs to create a Salesforce Maps Drive Profiles tab and a custom object for Maps Drive Profile3. Then, the user can create a new Drive Profile with the details of the vehicle and select it when creating a route in Salesforce Maps3. The characteristics of the vehicle’s Drive Profile will be used to create a route that is compliant with published permanent road restrictions3. Favorite Location, Schedule, and Marker Layer are not features that support the use of Custom Drive Profiles.

Balance prioritizes equal distribution of the selected attribute across territories in your focus. This is the best option for ensuring revenue is distributed as evenly as possible across the entire sales team1. References: Optimization in Salesforce Maps Territory Planning

According to the Trailhead module 3, this is the correct type of report and field for creating a data set that integrates with Enterprise Territory Management. An Accounts and Territories report can show the accounts that are assigned to territories, and the Territory Id field can be used to assign units to areas based on their territory membership.

Permission Groups are the permission level that an admin should review if a user is able to view but not able to export a list of markers from Salesforce Maps. Permission Groups are used to grant access to features in Salesforce Maps, such as allowing marker exports, editing details tab fields, enabling weather tab, and so on1. The admin can edit existing permission groups or create new ones to assign different features to different users or profiles1. If a user is not able to export a list of markers from Salesforce Maps, it means that the user does not have the ‘Allow Marker Exports’ permission checked in the Permission Groups on Maps configuration page2. The admin can enable this permission for the user or profile by editing the corresponding permission group2.

One way to automate the process of clearing coordinates for records that have address changes is to use a Salesforce automation tool, such as Process Builder or Flow Builder. These tools can help create workflows that trigger actions based on certain criteria or events. For example, the account executive from Alpine Energy can use Process Builder to create a process that runs whenever an account is created or edited,and checks if any of the address fields have changed. If so, the process can execute an action that clears the latitude and longitude values of the account record. This way, the next time the account is plotted on Salesforce Maps, it will geocode with the updated address and plot in the correct location. Alternatively, the account executive can use Flow Builder to create a flow that performs similar logic and actions as the process, but with more flexibility and customization options. For more information on how to use Process Builder or Flow Builder, see the references below. References:

• 2: Automate Your Business Processes with Process Builder | Salesforce Trailhead Module2
• 3: Automate Your Business Processes with Flow Builder | Salesforce Trailhead Module3

According to the Salesforce Help article on Publish to Enterprise Territory Management in Salesforce Maps Territory Planning2, three things that can be published from Territory Planning to Enterprise Territory Management are: manually assigned accounts, territories, and geographic territory rules. Manually assigned accounts are accounts that are locked to a specific territory in Territory Planning and will not be affected by optimization or rule changes2. Territories are the hierarchical units that define sales and service coverage areas3. Geographic territory rules are rules that assign accounts to territories based on their address fields4.

The implementation team is responsible for business and IT sanity testing post deployment to production. Sanity testing is a type of software testing executed on the stable build of an application with minor code changes. It is also known as surface-level testing. A sanity test is performed to ensure the application works as expected after the bug fixes or changes in the code1. The implementation team, which consists of developers, testers, and business analysts, conducts sanity testing to verify the functionality and performance of the application after deployment2. The project manager, the Salesforce support team, and the customer are not directly involved in sanity testing post deployment.

Analyze and Compare is a feature that can be used to view proposed changes before reassigning in Territory Planning. This feature allows users to compare different scenarios of territory alignment and see the impact of their changes on key metrics such as annual revenue, unit count, and workload balance. This feature can help users make informed decisions and optimize their territories for sales and service performance. This feature is explained in the Create an Optimal Territory Alignment document.

To create a custom data layer from a CSV file, the user needs to have two permissions assigned to the permission group they belong to: Manage Data Sources and Manage Data Layers. These permissions allow the user to upload external CSV files with record and location information, and create data layers to visualize this data in Salesforce Maps1. The user can create custom data layers from CSV files by following these steps2:

• Click Layers.
• To save the data layer privately so only you can see it, click Saved | Personal. Or, to share the data layer with other maps users, click Saved | Corporate.
• Hover over New and select Data Layer.
• Name the data layer and select the data source, filter, and style options you want the data layer to show.
• Click Choose data source and select Add a Data Source.
• Log in to the Salesforce Maps Custom Data Source Portal with your Salesforce credentials.
• Click + New to begin uploading a new external CSV file.
• Name your data source and click Upload Files to choose a local CSV file to upload as a data source.
• Select the location headers and the column headers you want to import from your CSV file, and format the data for each column header.
• Click Save and Process to upload your data source to Salesforce Maps.

References:

• 1: Custom Data Sources with Salesforce Maps | Salesforce Help1
• 2: Create Data Layers | Salesforce Help3

According to the Salesforce Maps documentation1, to create a data layer, the admin must first select either the Personal or Corporate folder in the Layers tab. The Personal folder is for saving data layers privately so only the admin can see them, while the Corporate folder is for sharing data layers with other maps users. After selecting a folder, the admin can hover over New and select Data Layer, then name the data layer and select the data source, filter, and style options. If the admin does not select a folder before attempting to create a layer, all of the options will be greyed out and unavailable. References:

• 1: Create Data Layers | Salesforce Help1

According to the Salesforce Help document 1, to enable task creation on mobile devices, the admin needs to update the assigned button set to include the “New Task” button. This will allow the sales reps to log a task on an account within the map view from their mobile device.

According to the Salesforce Help article on Routes and Schedule Settings in Maps2, you can enter your travel plans via the Maps Advanced Route tab to let the optimization engine know when and where you will be traveling. This will help you get more accurate routes that accommodate your travel plan.

The Analyze and Compare tool in Territory Planning is used to compare different alignments or scenarios and see how they differ in terms of key metrics, such as revenue, number of accounts, or workload1. This can help communicate to Sales Leaders or Sales Managers the impact of different planning scenarios on their territories and areas. The Analyze and Compare tool is not used to create a new alignment, as this requires using the Optimize tool1. The Analyze and Compare tool is also not used to add additional attributes to the Data Set, as this requires using the Data Set Configuration tool1.

According to the Trailhead module on Configure for Location Accuracy Unit3, one of the actions that an admin should do to ensure their Salesforce records plot in the correct location on the map is to confirm that each object to be used within Salesforce Maps has geolocation or number fields for latitude and longitude coordinates. These fields store the location data for each record and allow Salesforce Maps to read them when plotting data on the map3. Another action that an admin should do is to confirm that every record has a complete and valid address. This will help Salesforce Maps to geocode the records accurately and place them on the map based on their address fields4.

A communication plan is a best practice for any Salesforce implementation project, as it helps to inform and engage the stakeholders, users, and sponsors throughout the project lifecycle. A communication plan can include the project goals, benefits, timeline, milestones, roles and responsibilities, training and support resources, feedback mechanisms, and success metrics1. A communication plan can also help to address any potential resistance or challenges from the users or sponsors, and ensure a smooth adoption of the new solution2. References:

• 1: Salesforce Maps Configuration | Salesforce Trailhead Module2
• 2: Change Management Best Practices for Salesforce Administrators | Salesforce Trailhead Module3

3: https://trailhead.salesforce.com/en/content/learn/modules/change_management_best_practices_for_admins

Defining customer user stories is the process of identifying which user stories the implementation team will build based on the customer’s needs and priorities. Designing customer user stories is the process of determining how the implementation team will build the user stories based on the best practices and technical specifications. This is explained in the Salesforce Maps Implementation Methodology document.

Maps Live Layer and Maps Shape Layer are the two layers required to configure Live Rules. Live Rules are custom geofences that track whether a Maps Live Asset enters or exits a specific area5. To create a Live Rule, the user needs to select a Maps Live Layer and a Maps Shape Layer from the configuration options5. A Maps Live Layer is a layer that displays live location data of assets and drivers on the map3. A Maps Shape Layer is a layer that displays custom boundaries drawn on the map using polygon, circle, or rectangle tools6. These two layers define the assets and areas involved in the Live Rule. Maps Data Layer and Maps Marker Layer are not required for configuring Live Rules.

These are the three steps that the admin must complete to include their custom object Alpine Customers in Maps Advanced routing. According to the article "Configure custom routable object for Maps Advanced"1, a routable object is an object that represents the location users will navigate to within their Salesforce Maps Advanced Visit Plans, such as Accounts. To configure a custom object as a routable object, the admin needs to create a lookup relationship field on the Maps Advanced Route Waypoint object that points to the custom object1. The admin also needs to create a custom report type for the custom object in order to import the customer listfor routing2. Additionally, the admin needs to ensure that all records of the custom object have geocodes (latitude/longitude values) assigned, as this is required for plotting them on the map and routing them3. Making sure that Click2Create is configured for Alpine Customers is not a necessary step, as Click2Create is a feature that allows users to create records directly from the map view, not to include them in routing4. Ensuring that users are assigned to the records or related records they want to route via user lookup field is also not a necessary step, as this is only required for Enterprise Territory Management integration, not for routing5.

The most suitable publishing method in this scenario is Publish to CSV. This method allows the territory manager to export the alignment data to a CSV file, which can then be imported into Salesforce using a data loader tool. This method is recommended for large alignments with over 10,000 records, as it can handle high volumes of data and avoid performance issues. This method also allows the territory manager to review and modify the data before importing it intoSalesforce. This is explained in the Publish to CSV in Salesforce Maps Territory Planning document.

An administrator can assign users to a Maps Advanced Visit Plan by either selecting user profiles or individual users from the Users tab in the Visit Plan configuration. This is explained in the Assign Users to Your Visit Plan section of the Salesforce Help Docs.

The two permission sets that an admin must assign to a sales rep to enable their location tracking are SF Maps and SF Maps Live Mobile Tracking. These permission sets grant access to the Salesforce Maps app and the Salesforce Maps Live feature, which allow users to activate and deactivate live location tracking through their mobile device. The admin must also assign the corresponding permission set licenses and a Maps Permission Group with the Enable Live Mobile Tracking permission. This is explained in the Enable Live Location in the Maps App document.

According to the Salesforce Help article on Creating Visit Plans5, this is the correct order of steps for designing a process for Maps Advanced solutions. A visit plan contains the input for reps’ routes, such as datasets, calendar object, planning period, and optimization parameters5. After creating a visit plan, an admin can assign users or user profiles to it, so that they can generate routes based on the visit plan criteria5. Then, an admin can run optimization to create visits, which are individual stops on a route. Optimization takes into account various factors such as travel time, working hours, visit windows, and priorities5. Finally, users can view their visits in Salesforce Maps or Retail Execution app, and execute them according to their schedule6.

These are two factors that would cause them to use Schedule instead of Routes. Schedule is a feature that allows users to create and optimize a schedule of appointments for a day or a week3. Schedule requires all appointments to have a start and end time or duration4. Schedule also lets users sync their appointments with their Salesforce calendar as events3. This way, the users can plan around other events currently on their Salesforce calendar and avoid conflicts. Routes is a feature that allows users to create and optimize a route of stops for a daywithout requiring scheduled start and end times or durations3. Routes does not create Salesforce calendar events or sync with the Salesforce calendar5. Therefore, Schedule is more suitable for users who have meetings with fixed time slots and who want to coordinate with their Salesforce calendar.

These are the two options that an admin has when defining the Visit Duration in a Maps Advanced Visit Plan. Visit Duration is the amount of time that a user plans to spend at each stop on their route. The admin can configure the Visit Duration for a routable object in two ways:

• The admin can select a field from the routable object that contains the duration value, such as a custom field or a standard field like Estimated Travel Time. The field must be a number or text field that contains only numbers.
• The admin can enter any length of time in minutes in the Visit Duration field on the Maps Advanced Route Waypoint object. The Visit Duration field is a number field that accepts values from 1 to 1440 (24 hours). The admin cannot use fixed values like 60 minutes or 30 minutes as options for defining the Visit Duration, as these are not configurable options in Maps Advanced. The Visit Duration must be either a field from the routable object or a value entered in the Visit Duration field on the Maps Advanced Route Waypoint object.

According to the Trailhead module on Get to Know the Marker Layer Builder4, creating a marker layer follows the same process as creating a Salesforce report. Therefore, to test a marker layer and ensure Salesforce Maps is displaying the correct number of results, a user can create a Salesforce Report to match the Marker Layer Builder criteria4. This way, they can compare the results from both sources and identify any discrepancies or errors.

A visit plan can fail to populate any visits in the user’s calendar for several reasons. One possible reason is that the filters and spelling are incorrect or inconsistent, which can prevent the visit plan from finding the right customers or accounts. Another possible reason is that the customers are not within the driving range of the user, which can make the visit plan unfeasible or inefficient. A third possible reason is that there are too many customers assigned to the user, which can exceed the capacity or availability of the user. These reasons are explained in the Troubleshoot Visit Plans document.

To view household demographic data in the US, such as income, age, education, and population, the sales rep can use the Demographic Layers feature in Salesforce Maps. This feature allows the user to overlay demographic data on top of their existing data layers and visualize them with different colors and shapes. The Demographic Layers feature is described in the Get to Know Salesforce Maps unit.