Salesforce-Maps-Professional Questions and Answers

these are the two prerequisites for enabling live location tracking on mobile devices. The user needs to have the Maps Live Tracking permission set license and the Maps Live Tracking User permission set assigned to them. The user also needs to be assigned to a Maps Permission Group that has the ‘Enable Live Mobile Tracking’ permission enabled.

To see the five most recent Opportunities when a Sales Rep selects a pin from an Account Marker Layer, the developer should use the Related List Tab on the Marker Layer configuration. This tab allows the developer to add related objects to the marker layer and display them as a list when a pin is clicked. The developer can choose “Opportunities” from the “Add New” drop down and increment the Display counter to “5” to show only the five most recent Opportunities. The Related List Tab is explained in the Explore Salesforce Maps on Desktop unit.

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.

According to the Salesforce Help article on Understand and Troubleshoot Unit Assignment in Salesforce Maps Territory Planning5, two steps that a consultant can take to troubleshoot the issue of no units assigned to areas are: edit the data set, and see what field was used for Unit Assignment, and create a new alignment, and use the correct matching logic for this field; and edit the data set, and what report and/or queries were used to create it, and double check thatthe reports and/or queries return records when logged in as the OAuth user5. These steps willhelp ensure that the data set has valid unit assignment values and that there are no issues with data access or permissions5.

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.

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

Removing those accounts from focus or locking those units to the area are two options that a Consultant should recommend to prevent changes to key accounts during optimization in Territory Planning. Removing those accounts from focus means that they will not be included in the optimization process, while locking those units to the area means that they will not move during optimization, but the value of those units will be considered when creating balanced areas2. Leveraging a legend filter to remove those accounts or removing those accounts from the data set are not recommended options, as they will affect the accuracy and completeness of the data and the optimization results.

To select all of the containers in a particular state or province in Territory Planning, there are two ways: adding the state field to the container-legend and using it to search and select from the legend, or using the selection tools and selecting them from the map. Adding the state field to the container-legend allows the user to filter containers by state and select all containers that match a certain state value1. Using the selection tools, such as rectangle or polygon, allows the user to draw a shape on the map and select all containers that fall within that shape1. Using the state/province selection mode is not a valid option, as this mode is only available for units (accounts), not containers1. Adding the state field to the unit-legend is also not a valid option, as this will only allow selecting units (accounts), not containers1.

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.

The admin should add a filter to the Lead Marker Layer used to configure Stop Associations to include only open Leads. This will ensure that stops only be associated to open Leads in the Live Daily Summaries. The filter can be added on the Marker Layer configuration page by selecting the Filters tab and choosing the appropriate criteria for open Leads. This is explained in the Configuring Stop Associations for Live Daily Summary Configurations in Salesforce Maps document.

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.

Because Salesforce Maps is an installed package, its data and configurations cannot be moved via change sets. Change sets can only move metadata components between orgs, not data records or custom settings. Therefore, the Maps Administrator should consider recreating the Salesforce Maps data and configurations by hand in the destination org, or using a third-party tool or API to automate the process. This is explained in the Salesforce Maps Apex Developer Guide.

The sales manager is unable to publish the alignment because they only have Commenter access to the alignment, the alignment must be submitted for approval before publishing, and the alignment must be approved before it can be published. These are the three possible reasons that prevent the sales manager from publishing the alignment to Salesforce Maps. Commenter access only allows users to view and comment on alignments, but not edit or publish them. Submitting and approving alignments are required steps for publishing alignments if Alignment Approval is enabled in the org. These are explained in the Control Access to Alignments and Set Up a Process for Alignment Approvals and Publishing documents.

The two possible causes of this behavior are that the client is using a Professional edition Org which limits the number of records that can be processed using API, and that users are assigned to the Default Maps Permission group that has the Max Query Size defined to 5000. These factors can affect the number of records that users can plot on Desktop using their Account based marker layers. The Professional edition Org has a limit of 5,000 API calls per user license per 24-hour period, which can restrict the amount of data that Salesforce Maps can access and display. The Default Maps Permission group has a default setting of 5,000 for the Max Query Size, which can limit the number of records that users can query and plot on Desktop. These factors are explained in the Salesforce API Request Limits and Allocations document and the Salesforce Maps Permission Groups document.

According to the Salesforce Help article on Create Live Daily Summary Configuration in Salesforce Maps1, one of the steps to create a daily summary configuration is to select a preexisting live layer. The selected live layer specifies what assets and IoT devices will beincluded in the daily summary configuration1. A live layer is a layer that displays the current location and status of assets that are tracked by IoT devices2.

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 article on Enable Live Location in the Maps App3, one of the prerequisites for enabling live location tracking from the Salesforce Maps mobile app settings page is that the user must be assigned to a Maps Permission Group with the Enable Live Mobile Tracking permission enabled3. This permission allows users to activate and deactivate livelocation tracking through their mobile device3. If the user is not assigned to such a permission group, they will not have the option to enable live location in the app.

According to the Trailhead module 2, there are two possible reasons for missing markers on mobile devices compared to desktop devices. One is that the maximum records to plot setting for mobile is considerably less compared to desktop, which means that only a subset of records will be plotted on the map. The other is that the plot visible area feature is enabled, which means that only the records that fall within the current map view will be plotted.

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.

Creating a new alignment before optimizing on the correct attribute is the step that the user needs to take to return to the previous state prior to the optimization. A new alignment is a copy of an existing alignment that can be modified without affecting the original alignment3. The user can create a new alignment from the previous state and then run the optimization using the correct attribute. Clicking on the Undo button, creating a new data set, or re-running the optimization using the correct attribute are not valid steps, as they will not restore the previous state of the alignment.

Schedule is the feature that they should use to optimize their outside sales team’s time in the field and ensure that their stops appear in their Salesforce calendar as events. Schedule is a feature that allows users to create and optimize a schedule of appointments for a day or a week4. Schedule requires all appointments to have a start and end time or duration5. Schedule also lets users sync their appointments with their Salesforce calendar as events4. This way, the users can optimize their time in the field and keep track of their scheduled events. Click2Create is a feature that allows users to create records directly from the map view, such as leads or accounts2. Data Layers are layers that display data from Salesforce objects or external sources on the map6. Routes are features that allow users to create and optimize a route of stops for a day without requiring scheduled start and end times or durations4. These features are not relevant to the goal of optimizing their outside sales team’s time in the field and ensuring that their stops appear in their Salesforce calendar as events.

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.

Automatic route re-optimization is a feature that requires purchasing Salesforce Maps Advanced. This feature allows users to automatically adjust their routes based on real-time traffic conditions, customer availability, and other factors. This feature can help users save time, fuel, and money by finding the most efficient routes for their visits. This feature is explained in the Salesforce Maps Products document.

According to the Salesforce Help article on Plan My Visits1, this feature allows users to reoptimize their future routes based on their current schedule and visit plan settings. This way, users can ensure that any skipped or rescheduled visits are replanned according to their preferences and priorities1.

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.

 stop associations are a feature of Maps Live Tracking that allow an organization to see the accounts that are being visited during the day. Stop associations automatically link a user’s location history with nearby accounts, contacts, or leads in Salesforce. This way, an organization can track and analyze the visits made by their mobile users.