Support for records created outside of the Salesforce Maps user interface

This article answers why Salesforce Maps does not support creating or modifying records outside the Maps user interface, and what restrictions apply to automation on Maps managed package objects.

Why Records Must Be Created In-App

Salesforce Maps is built with a permission structure designed for in-app usage. When granting the Salesforce Maps permission set, users are given the appropriate permissions to read, create, edit, and delete the necessary Salesforce Maps records. The permissions used to restrict access, such as folder permissions, only restrict access when going through the Maps user interface. Salesforce Maps does not support creating items from outside the Maps user interface, including through Agentforce.

Restrictions on Automation, Sharing Rules, and Validation Rules

Note: We do not recommend creating any sharing rules or validation rules on the Salesforce Maps managed package objects or fields, as they may cause unforeseen errors or negatively impact app functionality. This includes modifying sharing settings, with the exception of making the Maps objects public for external users. We also do not recommend creating custom triggers or other automation on the managed package objects or fields, unless the automation is defined in the Salesforce Maps Developer Documentation. Several objects, such as Maps Routes and Maps Shape Layers, delete their related records upon editing or saving, which can cause unexpected behavior if automation is present. Salesforce Maps Support may require the deactivation or removal of these items to troubleshoot uncommon issues. Salesforce reserves the right to change features and functionality that are not being deprecated, such as object and field structure or vendors.