AX - Map
Overview
AX - Map is a Lightning App Builder component that displays your Salesforce records as interactive location markers on a map on record pages, app pages, and home pages.
Use it to visualize any records with location data—whether stored as addresses or latitude/longitude coordinates. Users can click markers to view record details, search and filter locations, and navigate directly to records on the map.
Perfect for territory planning, customer proximity views, asset tracking, service areas, or any scenario where geographic context helps users understand their data.
Getting Started
Use this simple tutorial to learn the basics of the Map component and start building your use cases.
Key features
Data Integration: Retrieves records from any Salesforce object as map markers.
Flexible Locations: Uses addresses or coordinates for marker placement.
Interactivity: Supports clickable markers, filters, search, and restricted map controls.
Customization: Dynamic titles, descriptions, and styled headers.
Dynamic Bindings: Leverages
{{Record.FieldApiName}}for context-aware displays.Visual Options: Card-style display and UI control toggles for tailored UX.
Component Comparison
This is a streamlined version of the Map component designed for quick implementation in Lightning App Builder's drag-and-drop interface. If you need more advanced options like custom marker styling, marker click actions, advanced map controls, custom popup designs, or specialized geolocation features, consider using the Map component in Dynamic Components for complete customization capabilities.
Use Cases
Account Page: Map related Contacts, offices, or site visits.
Opportunity Page: Visualize store or partner locations for deals.
Custom Object Page: Display service locations, delivery points, or project sites.
Sales Territory Dashboard: Show active Accounts or Leads by region with filters.
Service Operations Overview: Plot technician routes or case locations.
Event Planning View: Map event venues or marketing zones.
Configuration
Add the Map component to a Lightning Record Page in App Builder and configure via the Properties Panel.
Properties
Object Api Name
String
—
API name of the Salesforce object used to retrieve records displayed as map markers. Examples: Account, Lead, Custom_Object__c.
Filter
String
—
SOQL WHERE clause used to filter which records are shown on the map. Example: Status = 'Active' or Region__c = 'West'.
Order By
String
—
Field API name used to sort the records before display. Example: Name or LastModifiedDate.
Maximum Number of Records
Integer
—
The maximum number of records to retrieve and display as markers on the map. Helps manage performance and avoid clutter.
Title Field Name
String
—
Field API name used as the title for each marker. Examples: Name, Subject, or Title__c.
Description Field Name
String
—
Field API name used as the description for each marker. Examples: Description, Summary__c, Details__c.
Street Field Name
String
—
Field API name for the street address of a record. Example: BillingStreet, ShippingStreet.
City Field Name
String
—
Field API name for the city portion of the address. Example: BillingCity, ShippingCity.
Postal Code Field Name
String
—
Field API name for the postal or ZIP code. Example: BillingPostalCode, MailingPostalCode.
State Field Name
String
—
Field API name for the state or province. Example: BillingState, ShippingState.
Country Field Name
String
—
Field API name for the country. Example: BillingCountry, ShippingCountry.
Latitude Field Name
String
—
Field API name for the latitude coordinate (used when address fields are not provided). Example: Latitude__c.
Longitude Field Name
String
—
Field API name for the longitude coordinate (used when address fields are not provided). Example: Longitude__c.
Filter Fields
String
—
Comma-separated list of field API names displayed in the filter panel for user-driven filtering. Examples: Region__c,OwnerId,Type.
Metric Aggregation Fields
String
—
Show Search
Boolean
false
If true, displays a search bar above the map for keyword search on supported fields.
Disable Default UI
Boolean
false
If true, hides default map UI controls such as zoom buttons and street view toggle.
Disable Double Click Zoom
Boolean
false
If true, disables zooming via double-click.
Disable Dragging
Boolean
false
If true, disables the ability to move the map by dragging.
Disable Scrollwheel Zooming
Boolean
false
If true, disables zooming with the mouse scroll wheel.
Header - Title
String
—
Text displayed as the main title in the component header. Example: “Service Locations” or “Customer Map.”
Header - Caption
String
—
Subheading text displayed below the header title to provide context. Example: “Showing active accounts” or “Filtered by Territory.”
Header - Icon Name
String
—
SLDS icon name (e.g., standard:address) displayed beside the header title. Example: utility:map for geographic views.
Header - Show Number of Records
Boolean
false
If true, displays the total number of items in the map at the top of the component.
Action - Show More Details Panel
Boolean
false
If true, enables a side panel that displays additional record details when a row is selected, providing deeper context without leaving the page.
Action - Full Screen
Boolean
false
If true, displays a button that allows users to expand the data table to full screen, improving visibility for large datasets or detailed analysis.
Action - Enable Record Create
Boolean
false
If true, displays a button that allows users to create a new record in the map.
Display as Card
Boolean
true
If true, displays the map inside a styled card container for better visual presentation in dashboards or record pages.
Use Case Examples
Example 1: Account Contacts Map
Scenario: Display a geographic view of all contacts related to an account, showing their mailing addresses on an interactive map with role-based filtering for territory management.
Steps
Result: An interactive map showing contact locations with role-based filtering and clickable markers that provide contact details, perfect for territory planning and relationship management
Example 2: Accounts Map Overview
Scenario: Empower your sales team with a geographical overview of your company's accounts.
Customize Header
Set Header Title to
Accounts OverviewSet Header Caption to
World mapSet Header Icon Name to
standard:accountCheck Disable Dragging to prevent accidental map movement
Check Show more details panel to activate a side panel when users click on a record
Check Enable record create to let your users create accounts directly from the map
Example 3: Service Locations Dashboard
Scenario: Create a comprehensive dashboard view of active service locations using GPS coordinates, with regional filtering and search capabilities for operational management.
Prerequisites: This example assumes you have created a custom Service Location object (Service_Location__c) with custom fields including Status__c (picklist for Active/Inactive), Latitude__c and Longitude__c (number fields for GPS coordinates), and Region__c (picklist or text field for geographic regions).
Steps
Result: A professional dashboard map showing active service locations with regional filtering, search capabilities, and detailed location information accessible through interactive markers
Key Considerations
Location Fields: Use address fields for geocoding or lat/long for precision; ensure at least one set is mapped.
Dynamic Bindings: Leverage
{{Record.FieldApiName}}for filters/headers on Record Pages.Performance: Set limit for large datasets; test filters to avoid overload.
Map Controls: Disable dragging/zooming for static views; keep UI for interactive dashboards.
Interactions: Bind marker data (e.g., ID via titleFieldName) for navigations or flows.
Accessibility: Ensure clear titles/captions; test marker clickability with keyboards.
Troubleshooting Common Issues
No Markers Shown: Verify sObjectApiName, filter, and location fields (address or lat/long); check permissions.
Bindings Fail: Confirm
{{Record.FieldApiName}}context; test in Record Page preview.Filters/Search Missing: Enable showSearch/filterableFields; map relevant fields.
Map Not Interactive: Check disableDragging/disableDefaultUi are Off; test permissions.
Marker Overlap: Use limit to reduce markers; consider clustering in Screen Flows.
Layout Issues: Adjust Style Panel for size/margins; test card display on mobile.
Need More Advanced Features?
This App Builder version provides essential mapping functionality with simple configuration. For advanced capabilities like custom marker designs, interactive click actions, and specialized geolocation workflows, explore the Map component in Dynamic Components for more customization options.
Last updated
Was this helpful?
