Loading

Screen Flow and Lightning Web Component Limitations in Salesforce Maps.

Publiseringsdato: May 4, 2026
Beskrivelse

When using flows, aura-based Lightning components or lightning web components (LWC) from Salesforce Maps - there are limitations that fall outside the Maps product, but can hinder certain functionalities. These limitations are encountered via the Mobile experience and/or via the Desktop app

Løsning

The following table describes known limitations when using Screen Flows, Aura-based Lightning components, and Lightning Web Components (LWC) as Custom Actions inside Salesforce Maps, along with available workarounds.

 

Known IssueDescriptionProducts AffectedWork Arounds
Lookup fields do not display optionsWhen using a lookup field in a screen flow launched on a mobile device from inside of Salesforce Maps, the lookup overlay does not render for the interacting user.Mobile

This is currently expected behavior. There is no workaround to avoid this behavior at this time.

Popups and Events included in flows and Lightning components do not display when launched via Maps
When using a screen flow or Lightning component launched inside of Salesforce Maps via desktop or a mobile device, popups and events will not display as all components must be contained. The event panel is not a currently supported Lightning feature inside of Salesforce Maps.
 		Desktop, Mobile
 		This is currently expected behavior. There is no workaround to avoid this behavior at this time.
Quick Lookups display incorrect object resultsWhen using a quick lookup component within a screen flow or Lightning component launched inside Salesforce Maps on a desktop, the quick lookup component doesn't return object records according to what the field suggestsDesktopIn the quick lookup component file, add an access property and set it to"global" in all of the aura:attribute
Knowledge-artikkelnummer

000390452

 
Laster
Salesforce Help | Article