Salesforce Salesforce-Maps-Professional SalesforceMaps Accredited Professional (SU24) Exam Practice Test

heatmap is a render mode that can display closely-related markers colored according to their density. A heatmap is a graphical representation of data where the individual values contained in a matrix are represented as colors. A heatmap can show the intensity of data points in an area, such as the number of customers or sales volume.

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, the account 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

An administrator can assign users to a Maps Advanced Visit Plan by either selecting user profiles or individual users from the Users tab in the Visit Plan configuration. This is explained in the Assign Users to Your Visit Plan section of the Salesforce Help Docs.

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.

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 Visualizing Live Asset Tracking History in Salesforce Maps1, one way to visualize the Accounts visited by a team on a specific day is to plot a Live Layer and generate tracking history. This will display the historical location and travel of the Asset, plus the locations of any Stop, Speeding, and Safety Events captured by the Asset’s IoT Device for a desired date range1. Another way to visualize the Accounts visited by a team on a specific day is to create a Salesforce report for Accounts with Maps Live Event Association records2. This will show the Accounts that have been associated with Stop Events based on the configuration of Stop Associations in Salesforce Maps Live2.

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.

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.

According to the Salesforce Help article on Configure Options for Publishing Alignments1, one of the possible causes of some publish options being greyed out and inactive is that the user does not have the correct permission to publish. The admin can configure the access level and approval requirement for each publish option in the Salesforce Maps package settings1. If the user is not assigned to a permission group or profile that has the access level to publish, they will not be able to use that option1.

Salesforce Maps allows users to check in and check out of tasks, events, and other records from the map interface. This feature helps users track their activities and log their visits. However, some users may forget to check out of a task when they leave an appointment, which can cause inaccurate data and reports. To prevent this, an admin can enable the “Auto Check Out” feature for the corresponding Base Object under Installed Package | Configure | Base Objects. This feature automatically checks out a user from a record when they move away from the location by a certain distance. The admin can specify the distance threshold and the time interval for the auto check out feature. This way, the users do not have to manually check out of a task, and the data is updated automatically. References: Salesforce Maps User Guide, Salesforce Maps Check In and Check Out, Salesforce Maps Base Objects

According to the Trailhead module 2, this is the best strategy for creating a data set with a large number of accounts. A single SOQL query can retrieve up to 500,000 records, and aggregating to the container level can reduce the number of units in the data set. This can improve the performance and efficiency of Territory Planning.

According to the Trailhead module 3, this is the correct type of report and field for creating a data set that integrates with Enterprise Territory Management. An Accounts and Territories report can show the accounts that are assigned to territories, and the Territory Id field can be used to assign units to areas based on their territory membership.

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.

The implementation team is responsible for business and IT sanity testing post deployment to production. Sanity testing is a type of software testing executed on the stable build of an application with minor code changes. It is also known as surface-level testing. A sanity test is performed to ensure the application works as expected after the bug fixes or changes in the code1. The implementation team, which consists of developers, testers, and business analysts, conducts sanity testing to verify the functionality and performance of the application after deployment2. The project manager, the Salesforce support team, and the customer are not directly involved in sanity testing post deployment.

To create a data set that includes account data from Salesforce and attribute data from an external source, the customer has three options:

• A. SOQL Queries: The customer can use SOQL queries to pull data from Salesforce objects and fields, and join them with external data sources, such as CSV files or web services. SOQL queries allow the customer to specify complex filters and conditions to select the relevant records and fields for the data set1. The customer can create SOQL queries in the Data Sets tab in Maps Advanced, by clicking New, selecting the object type, and choosing SOQL Query as the data source2.
• C. Salesforce Reports: The customer can use Salesforce reports to create data sets that include data from multiple objects and fields, such as accounts, contacts, opportunities, and custom objects. Salesforce reports allow the customer to use report types, filters, groupings, and charts to customize the data they want to plot on the map3. The customer can create Salesforce reports in the Reports tab in Salesforce, and then use them as data sources in the Data Sets tab in Maps Advanced, by clicking New, selecting the object type, and choosing Report as the data source4.
• E. External CSV: The customer can use external CSV files to import data from other systems or applications into Salesforce Maps. CSV files are comma-separated values files that store tabular data in plain text format. CSV files can include data from various sources, such as spreadsheets, databases, or web services. The customer can upload CSV files as data sources in the Data Sets tab in Maps Advanced, by clicking New, selecting the object type, and choosing CSV File as the data source5.

References:

• 1: Create Data Sets from SOQL Queries | Salesforce Help6
• 2: Create Data Sets | Salesforce Help7
• 3: Reports: The Building Blocks of Analytics | Salesforce Trailhead Module8
• 4: Create Data Sets from Reports | Salesforce Help9
• 5: Create Data Sets from CSV Files | Salesforce Help

 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.

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.

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 Consultant should recommend Publish to Salesforce Fields as the publish method in Territory Planning for a client who uses account owners as the primary method of territory assignment and has low influx of new accounts. This method allows users to update any field on any object with the territory name or ID. This can be useful for clients who want to assign accounts based on ownership and do not need to update them frequently. This method also works well for non-contiguous territories, as it does not rely on geographical boundaries. This is explained in the Publish to Fields in Salesforce Maps Territory Planning document.

These are two considerations that a Salesforce admin should keep in mind when setting up the OAuth user in order to establish a secure connection with the Salesforce Maps Routing Engine. An OAuth user is required to perform optimizations for routes in Advanced Routing4. The OAuth user should have the following permissions and roles6:

• The OAuth user should have the Salesforce Maps Advanced Permission Set License assigned.
• The OAuth user should have the Maps Admin and SF Maps Advanced Permission Sets assigned.
• The OAuth User has been assigned to a role that is above the Maps Advanced end-users in the Salesforce Role Hierarchy. The OAuth user does not need to be assigned to an active visit plan, as this is not relevant for setting up an OAuth user. The OAuth user does not need to be assigned to the ‘OAuth user’ profile, as this is not a valid profile in Salesforce.

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.

According to the Trailhead module on Get to Know the Marker Layer Builder4, creating a marker layer follows the same process as creating a Salesforce report. Therefore, to test a marker layer and ensure Salesforce Maps is displaying the correct number of results, a user can create a Salesforce Report to match the Marker Layer Builder criteria4. This way, they can compare the results from both sources and identify any discrepancies or errors.

According to the Trailhead module 3, the import from alignment feature allows planners to import existing territory boundaries from a previous alignment into a new data set and alignment. This way, they can avoid redrawing the boundaries every time they create a new data set and alignment. This feature is useful for companies like Alpine Energy that realign their sales territories quarterly and want to preserve their previous alignments.

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.

A Salesforce Maps Solution Architect should have excellent verbal and written communication skills, understanding of design pitfalls and mitigation actions, and being effective at planning, monitoring, and reviewing Maps customer use cases to successfully scope the project. These abilities are essential for gathering and analyzing the customer’s requirements, designing and proposing the best solution, and ensuring the quality and satisfaction of the implementation. These abilities are also part of the Salesforce Maps Solution Architect Certification exam guide.

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.

According to the Salesforce Help article on Optimization in Salesforce Maps Territory Planning2, pinned area centers are fixed locations that optimization uses as starting points for each territory. This feature can be used to ensure that sales reps’ homes are located within theboundaries of their respective territories whenever they run an optimization2. Pinned area centers can be set manually or automatically based on user location or other criteria2.

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

• 1: Salesforce Maps Configuration | Salesforce Trailhead Module2
• 2: Change Management Best Practices for Salesforce Administrators | Salesforce Trailhead Module3

3:

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 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 the Interact with Salesforce Maps on Mobile document.