Salesforce Certified Maps Professional Practice Test - Questions Answers, Page 5

The user should tap the refresh button located at the bottom of the map to display additional accounts. This button reloads the marker layer data based on the current map view and filters. This is useful when the user changes the map view by zooming in or out, or panning across the map. This is explained in theInteract with Salesforce Maps on Mobiledocument.

The sales managers should use Maps Advanced and create logical visit plans to ensure a logical routing structure for door to door sales and cover all houses on one street before moving to the next. Maps Advanced allows users to create visit plans based on various criteria, such as frequency, priority, location, and availability. Users can also use logical visit plans, which are a type of visit plan that assigns visits based on proximity and order. This can help users visit all the houses on one street before moving to the next, and reduce travel time and distance. This is explained in theCreate a Logical Visit Plandocument.

According to the Salesforce Maps Configuration module on Trailhead1, to create multiple visit windows for different types of visits, you need to create two lookup fields on the Account object to the Visit Window object. This way, you can assign different visit windows to different routable records.

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.

According to the Salesforce Help article on Compare Maps Route and Schedule3, the optimization engine in Territory Planning takes into account three factors: Areas/Units in Focus, Geography, and Selected Optimization Field/Attribute. These factors help you design optimal territories based on your business goals and constraints.

According to the Salesforce News article on Salesforce Products Get More Inclusive with New Gender Identity and Pronoun Data Options1, the new fields for gender identity and pronoun data are part of Salesforce's core objects, which means they are populated through most of its products and available by default.Therefore, to expose the Preferred Pronoun field for each Contact record inside the Maps app, an admin can use the Tooltips tab in the Marker Layer builder to show the Preferred Pronoun field2. This way, when a user hovers over a marker on the map, they can see the preferred pronoun of the contact along with other information.

According to the Salesforce Help article on Filter by Owner in Maps Marker Layer Builder3, filtering by owner or ownership scope allows Maps users to filter Marker layers based on the record ownership model in their Salesforce org.To create one marker layer for several users to display only the accounts they currently own, an admin can create an Account Marker Layer, select My Accounts under Filter By Owner3. This will show all accounts owned by the logged-in user.

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 theTroubleshoot Visit Plansdocument.

A stop can fail to associate with a nearby account for two main reasons. One is that the account record is not geocoded, which means that it does not have a valid latitude and longitude value. This can prevent the stop from finding the account on the map. The other reason is that the account record is not included in the Marker Layer used to generate stop associations, which means that it is not part of the data set that the stop is looking for. This can happen if the account does not meet the criteria or filters of the Marker Layer. These reasons are explained in theAssociate Stops with Accountsdocument.