Pass the Salesforce Salesforce-Maps-Professional Salesforce-Maps-Professional Questions and answers with CertsForce

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.

The shift length is too short. This could be the cause of the error when trying to optimize the route with 124 customers. The shift length is the maximum amount of time that a user can work in a day, and it is set in the visit plan settings. If the shift length is too short, it may not be possible to visit all the customers within the time limit, and the optimization may fail. To avoid this error, the administrator should increase the shift length or reduce the number of customers in the dataset. This is explained in the Specify Visit and Optimization Parameters document.

The Admin should enable “Allow Route/Schedule Sharing” to ensure all Maps Users can see each other’s Routes and Schedules. This setting allows users to share their Routes and Schedules with other users in their org, and also view the Routes and Schedules of other users who have shared them. This setting can be found in the Routes and Schedule settings within Maps Configuration. Thisis explained in the Routes and Schedule Settings in Maps document.

Acommunication 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 andresponsibilities, training and support resources, feedback mechanisms, and success metrics1. A communication plan can also helpto address any potential resistance or challenges from the users or sponsors, and ensure a smooth adoption of the new solution2. References:

1: SalesforceMaps 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

The most suitable publishingmethod 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 into Salesforce. This is explained in the Publish to CSV in Salesforce Maps Territory Planning document.

These are two factors that an admin should keep in mind during the oAuth process when setting up Maps Advanced. According to the article "OAuth user requirements for Salesforce Maps"1, an oAuth user is required to establish a secure asynchronous connection with the Salesforce Maps Advanced, Live Tracking, and Territory Planning products. The oAuth user impacts the following product functions:

Performs optimizations for routes in Advanced Routing

Uploads results of Live Rules into customer Org in Live Tracking

Performs optimizations for territories in Territory Planning To perform these functions, the oAuth user should have full CRED (Create, Read, Edit, Delete) rights for records being routed1. The oAuth user should also beassigned a role that is above the Maps Advanced end-users in the Salesforce Role Hierarchy1. This ensures that the oAuth user can access and modify the records ofthe end-users. Having the SF Maps Admin permission set is not the only prerequisite for the oAuth user, as the oAuth user also needs to have the Salesforce MapsAdvanced Permission Set License assigned and the SF Maps Advanced Permission Set assigned1. The oAuth user does not need to fall within Sales organization, as this is not a relevant factor for setting up Maps Advanced.

Developer and Technical Architect are two team members that should be included during a Maps scoping session in which legacy data/mapping system migrations and integrations/interfaces will be discussed. These team members have the technical expertise and skills to assess the feasibility, complexity, and risks of migrating and integrating data from different sources and systems. They can also provide guidance and recommendations on how to design, develop, test, and deploy the data migration and integration solutions. These team members are part of the Salesforce Maps Implementation Methodology document.

The team at Alpine Energy can leverage Promotional Windows to prioritize visits to the subsetof the targeted customers. Promotional Windows are a feature in Maps Advanced that allow users to create temporary changes in visit frequencies for specific customers or datasets. This way, they can maintain their standard cadences with their customers, but also focus on the new product launch for a certain period of time.

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, theaccount 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

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 isthat 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.