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.

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.

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.