Salesforce-Maps-Professional Exam Dumps : SalesforceMaps Accredited Professional (SU24)

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.

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.

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 theaccount does not meet the criteria or filters of the Marker Layer. These reasons are explained in the Associate Stops with Accounts document.