Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Exam Salesforce Maps Professional Topic 1 Question 21 Discussion

Actual exam question for Salesforce's Salesforce Maps Professional exam
Question #: 21
Topic #: 1
[All Salesforce Maps Professional Questions]

What are two common reasons why a new account marker layer would display an error for "bad addresses?"

Show Suggested Answer Hide Answer
Suggested Answer: A, B

A new account marker layer may display an error for ''bad addresses'' if the address on the account record is unknown or invalid, or if the base object has not been configured correctly. A bad address means that the record failed to plot on the map, and it can affect the accuracy and completeness of the data visualization. To fix this issue, the user can either drop a pin on the map to manually set the location of the record, or clear the coordinates and set the verified location by dragging the marker. The user can also check the base object configuration under Installed Package | Configure | Base Objects and make sure the address fields are mapped correctly.Reference:How to handle Maps bad addresses,Drop a pin for bad addresses in Maps,Salesforce Maps Base Objects


by Florencia at Jun 21, 2024, 12:11 AM

Limited Time Offer

25%

Off

Get Premium Salesforce Maps Professional Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Trinidad
5 months ago
I think the Salesforce record being deleted could also cause the error.
upvoted 0 times
...
Catarina
5 months ago
Haha, I bet the person who wrote this question was just trying to trip us up with all those distractors. B and D are the obvious choices, but I'm keeping an eye out for any sneaky trick questions!
upvoted 0 times
Lacresha
4 months ago
Good point, that could definitely cause the error as well.
upvoted 0 times
...
Zana
4 months ago
I'm going with D) The Account Marker Layer's filters need to be adjusted.
upvoted 0 times
...
Nada
4 months ago
Yeah, that seems like a common reason for the error.
upvoted 0 times
...
Josphine
4 months ago
I think it's B) The address on the Account record is invalid.
upvoted 0 times
...
...
Brande
5 months ago
I believe the error could also be due to the Account Marker Layer's filters needing adjustment.
upvoted 0 times
...
Lawanda
6 months ago
I agree with Janey. The address on the Account record might also be invalid.
upvoted 0 times
...
Clarence
6 months ago
This is a tricky one, but I agree that B and D are the best answers. Although C could also be a possibility if the Salesforce record was accidentally deleted.
upvoted 0 times
...
Yvonne
6 months ago
Hmm, I'm thinking B and D as well. The account address and the layer's filters are probably the two main culprits here.
upvoted 0 times
Billye
5 months ago
Yes, and adjusting the filters on the Account Marker Layer might also solve the problem.
upvoted 0 times
...
Francisca
5 months ago
I agree, the address on the Account record could be the issue.
upvoted 0 times
...
...
Juan
6 months ago
I'd go with B and D. If the address is invalid or the filters aren't configured properly, that could definitely lead to the 'bad addresses' error.
upvoted 0 times
...
Jerry
6 months ago
B and D seem like the most likely reasons. The address on the Account record being invalid or the filters needing adjustment would both cause issues with the new account marker layer.
upvoted 0 times
Haydee
5 months ago
It's important to double check both the address on the Account record and the filters for the marker layer.
upvoted 0 times
...
Kristel
5 months ago
I agree, but D could also be a factor. Filters needing adjustment can lead to issues as well.
upvoted 0 times
...
Mica
5 months ago
I think B is the most common reason. Invalid addresses can definitely cause errors.
upvoted 0 times
...
...
Janey
6 months ago
I think the error could be because the Base Object is not configured correctly.
upvoted 0 times
...

Save Cancel