Maps marker layers show no results when using custom object Location as base object

This article explains how to work around the naming collision between a custom "Location__c" object and the managed package's own "Location" object so your records plot correctly.

Cause

The "maps__" namespace is appended to the query, which defaults to the "Location" object within the Salesforce Maps managed package instead of your custom "Location__c" object — even though your Base Object is meant to reference your own custom object.

Fix

If your Maps Base Object references the Location object for its address fields, the only workaround is to change the API name of your custom location object. If your Base Object is built from another object but uses the location object as its address location, we recommend creating formula fields to pull in the required address and coordinate fields so the records can plot.

Related Naming Collisions

Note: This issue can occur for any custom object that shares the same naming convention as objects in the managed package, e.g., Route__c and maps__Route__c. See this Idea for more information.