LWR | Salesforce Trailblazer Community

Is Salesforce Maps officially supported in an Experience Cloud LWR site?

Hi everyone,

We have a requirement to display the native Salesforce Maps managed-package UI inside an Experience Cloud LWR site, specifically within an OmniScript.

We have confirmed that Salesforce Maps itself is working correctly in our org. The managed-package Visualforce page:

/apex/maps__Maps

successfully loads the full Salesforce Maps UI for internal Salesforce users, including Layers, Routes, Schedule, List, and configured Maps layers.

We also found Salesforce's official documentation stating that

Experience Cloud site users can access Salesforce Maps

, including guidance around Maps permission sets, permission groups, sharing settings, and Maps Community user licenses.

However, our site is an

LWR Experience Cloud site, and we haven't found official documentation that specifically confirms whether the native Salesforce Maps UI can be rendered inside an LWR site

We have tried the following approaches:

Native Salesforce Maps Aura component — not available because our site is LWR.
Visualforce Page component in Experience Builder — not available in our LWR site's component palette.
maps:MiniMapLightningComponent through maps:MapsLightningOutApp — fails from the portal context during the Lightning Out authentication/bootstrap process.
Salesforce Maps managed VF page through /vforcesite/maps__Maps — the page loads but internally attempts to load maps__MapsLightningOutApp, which results in a 404 in the Experience Cloud domain.
Direct /apex/maps__Maps URL — works for an internal Salesforce user, but an Experience Cloud portal user is redirected to the Salesforce login page because the portal session does not carry over to the Salesforce domain.

Our Experience Cloud users also have the appropriate Salesforce Maps access/permissions configured.

My question is:

Does Salesforce currently officially support rendering the native Salesforce Maps UI inside an Experience Cloud LWR site?

If yes:

What is the officially supported implementation approach?
Is there an LWR-compatible Salesforce Maps LWC or component?
Is Lightning Out 2.0 supported for Salesforce Maps in an LWR Experience Cloud site?
Is there a supported way to embed the maps__Maps Visualforce page for an authenticated Experience Cloud LWR user?
Are there any additional configuration requirements for the Salesforce Maps domain/session to work with LWR?

If LWR is

not currently supported, is Salesforce Maps LWR compatibility on the roadmap, or is an Aura-based Experience Cloud site currently required

for the native Salesforce Maps experience?

#LWR

1 answer

Himanshu Shekhar (AQBEE Innovations Pvt. Ltd.)
Aug 20, 5:51 PM
Hi Prajwal - short answer: the native Salesforce Maps managed-package UI is not supported as a component inside an LWR site, and it is an architecture limit rather than a Maps-specific one. LWR runs Lightning Web Components ONLY - it cannot run Aura components or Visualforce pages (that is the big difference from Aura-based Experience Cloud templates, which run both). The full Maps UI (Layers/Routes/Schedule/List) is delivered through that Visualforce/Aura managed-package page, so it has nothing to render as a native LWR component.

The docs you found ('Experience Cloud users can access Salesforce Maps') are about licensing, permission sets, and Aura-based site access - not LWR component support. So there is no official 'drop Maps into an LWR page/OmniScript' path.

Realistic options:
1. iframe the Visualforce Maps page inside a custom LWC that you place on the LWR page/OmniScript. Caveats: add the VF domain to CSP Trusted Sites, and mind the session - it works for authenticated site users who have the Maps licenses/permission sets, but guest-user access to the VF page is the usual sticking point.
2. Build a custom LWC using the Maps data (query the geolocation/records and plot them with lightning-map or a JS mapping library). More effort, but fully LWR-native and OmniScript-friendly.

If you truly need the full native Maps UI (not just a map), the iframe route is the only realistic one in LWR - just validate it against your guest-vs-authenticated user model early.

If this helps, please mark it as the Best Answer so it helps the next person - thanks :)

Add a comment

Write an answer...

0/9000

Sep 15, 2025, 4:15 PM

I have found a bug with LWR Experience Builder's screen responsive property setting for Text Blocks.

Here is how I assume this is supposed to work:

I place a text block in Experience Builder.
I check "Override style's default HTML tag".
I set HTML tag to H1
I set Text Style to Heading 1.
I switch to Mobile View Mode.
I select text block.
I change Text Style to Heading 6.

At this point, what should happen is that on desktop screen sizes, that text block will have an <h1> HTML tag, and the text style will use the Heading 1 styles. On mobile screen sizes (less than 768px), that same text block will have an <h1> HTML tag, but the text still will now use the Heading 6 style.

Here is what is actually happening.

When I follow those steps in Builder & Preview Mode, it appears to be working correctly. However, when I publish the site here is what I see:
In Desktop browser sizes, the text block has <h1> as HTML tag and Heading 1 styles.
In mobile browser sizes, the text block has <h1> as HTML tag, but it still has Heading 1 styles except for the font weight. The font weight of the text block has changed to the Heading 6 style, but everything else about it is using the Heading 1 style.

Here are the text theme settings for Heading 1 and Heading 6 I have found a bug with LWR Experience Builder's screen responsive property setting for Text Blocks. Here is how I assume this is supposed to work:I place a text block in Experience Builder.

I have found a bug with LWR Experience Builder's screen responsive property setting for Text Blocks. Here is how I assume this is supposed to work:I place a text block in Experience Builder.

Here are the Desktop View Mode property settings for that text block.

Here are the Mobile View Mode property settings for that text block.

Here's how it looks in Preview Mode when switching between viewport mode (notice the text size gets smaller and it gets bold).

Here's how the published site looks when changing browser sizes (notice the text doesn't change size, it just gets bold):

I have attached a screen recording of this happening.

I have already create a support ticket:

Case #471481270

Case Title: Text Block screen responsive property settings do not work

Here is the live published page:

https://trifectatechnologies84-dev-ed.develop.my.site.com/byo2026/

@George Abboud @Alicia Teo @Julie Thompson @* Experience Cloud * #LWR #Experience Builder

exp-responsive-text-settings.mp4

1 comment

Jason Kilp (Trifecta Technologies)
Sep 16, 2025, 6:44 PM
There is a Known Issue for this: https://help.salesforce.com/s/issue?id=a028c00000zjpXC

If anyone else runs into this issue, there is a workaround:
On desktop view, add in a text block component.
Check "Override style's default HTML tag".
Make sure the Style is set to something different than the HTML tag. For instance, if the HTML tag is set to "h1", set the Style to "h3".
Switch to mobile view.
Change the style of that text block to be what you want.
Go back to mobile view.
Change the style of the text block to be what you want.
What seems to be happening is if when you first place that text block, and you check "Override styles.." but then set the HTML tag and the style to be the same (e.g. Heading 1 style and h1 tag), then change it in mobile view, it messes it up.

Add a comment

Write a comment...

0/9000

Jul 17, 2025, 3:18 PM

Hide standard fields from Results Layout filters

Is there any way to remove all of these filters? They are standard fields on Knowledge Articles and can't be removed from the search layout. These aren't fields that our portal users need to see or know about or even be able to search. Even if there is a CSS hack to hide them, I'd be OK with that.

6 answers

Chris Rouse (Amplify, Inc)
Aug 5, 2025, 7:51 PM
"Change the search layout" is not the right answer. That changes which fields show up in the search results such as title, date, summary, whatever. It does not impact the filters.

"Change the search manager" is also wrong because you can't remove required fields.

I grabbed the HTML for the Filters section and passed it into Claude and asked for the CSS to target each filter and it was able to eventually work it out

Here's the code that you need to your LWR site to hide all of the filters. Comment out any lines for filters you want to keep.

<style>
lightning-combobox:has(button[aria-label="Language"]),
lightning-combobox:has(button[aria-label="Publication Status"]),
lightning-combobox:has(button[aria-label="Products"]),
lightning-combobox:has(button[aria-label="Audience"]),
lightning-combobox:has(button[aria-label="Issues"]),
search_filters-filter-input:has(button[aria-label="Language"]),
search_filters-combobox:has(button[aria-label="Language"]),
search_filters-combobox:has(button[aria-label="Publication Status"]),
search_filters-combobox:has(button[aria-label="Validation Status"]),
search_filters-combobox:has(button[aria-label="Article Record Type: Name"]) {
display: none !important;
}
</style>

#LWR

Add a comment

Write an answer...

0/9000

Nov 8, 2024, 8:59 PM

Idea Exchange Post - Experience Builder Rich Content Editor Enhancements

EDIT: The idea I posted got merged with an existing one. I've posted both URLs, but there is only one you can vote on now.

New URL (can vote on this one)

https://ideas.salesforce.com/s/idea/a0B8W00000QcUVDUA3/lwr-rich-content-editor-component-should-allow-us-to-use-theme-styles

Old URL (this is now archived)

https://ideas.salesforce.com/s/idea/a0B8W00000Qen1SUAR/experience-builder-rich-content-editor-enhancements

--- previous post ---

Hi everyone, I've added an idea to Idea Exchange to enhance Experience Builder's Rich Content Editor component. It feels very outdated and is missing a lot of features. If you could take a look and upvote if you agree that would be wonderful!

Here's what's in the idea:

Color Picker

Theme Colors: Include colors from theme settings, similar to PowerPoint, where theme colors are shown with various shades in the color picker.
Manual Color Selection: Allow manual color selection using color codes like hex, rgba, etc.

Fonts

Theme Fonts: Offer fonts from the theme settings as default options in the font selector.
Full Font Selection: Allow us to choose from all fonts available in the theme settings.

Heading Levels & HTML Semantics

Heading Levels: The LWR version currently allows only font size selection, not heading levels, which removes semantics and accessibility from the text. Please bring back the option to select heading levels.
Content Record Semantics: When content with heading levels is saved in a CMS content record, those semantics are stripped out in the Experience Builder’s rich content field. This should be fixed.

Images

Allow images pasted into the editor to stay visible after exiting the editor. Currently, pasted images disappear once you leave the editor.

Markdown Support

Enable markdown syntax formatting to streamline adding structure to content. This would also require bringing back HTML semantics for full compatibility.

Links

Include expressions in the “Add a Link” modal, allowing users to easily link to specific pages within the site without manually entering the full URL.

Merge Fields

Add a menu button to insert merge fields, making it easier to display dynamic content without memorizing expressions.

Code View

Offer a code view mode to allow basic HTML elements for enhanced content customization—this is a standard feature on many CMS platforms.

#Experience Cloud #IdeaExchange #LWR

Add a comment

Write a comment...

0/9000

Oct 23, 2024, 12:45 PM

Learn More About: LWC Local Dev

The beta of LWC Local Dev was one of the biggest announcements for developers at #Dreamforce2024. With Local Dev you can get a preview of your components just by saving your code, which makes you a much more productive developer.

This means that you can save 3-10 seconds of wait time per component update, and when you spend days working on an #LWC development, this quickly adds up to hours saved.

Local Dev works across various Salesforce containers, such as Lightning Experience, #LWR sites for @* Experience Cloud *, and the Salesforce mobile app.

To learn more about this feature and how it works behind the scenes, check out these great resources from Developer Advocate @Alba Rivas:

📽 Watch a video

📖 Read a blog

If you have feedback or questions about Local Dev, post them in the @LWC group, using #LWC Local Development tag.

Learn More About: LWC Local Dev The beta of LWC Local Dev was one of the biggest announcements for developers at .

3 comments

Hemanth Sunkara (aditya college of engineering)
Oct 25, 2024, 2:03 AM
Lp
Lll

Add a comment

Write a comment...

0/9000

Sep 21, 2024, 2:22 PM

How to uniquely load the cart items for a guest user ?

How to identify and load the guest cart items in LWR b2b sites ?

We cannot rely on a common account ID to fetch cart items. This will lead to bad user experience.

Any assistance would be greatly appreciated

#B2B Commerce #LWR

1 answer

Mary Jennings (Forim)
Sep 22, 2024, 6:23 PM
Hi @Gnanesh Challa,

you can consider using browser-based tracking methods like cookies or local storage.

1. Generate a unique session ID for each guest user when they first add an item to the cart.
2. Store the session ID in a cookie or local storage in the user's browser. When the user interacts with the cart, use this session ID to retrieve the cart items from your backend, ensuring each guest has a unique experience.
3. Ensure the session persists until the cart is checked out or abandoned. This way, the experience remains consistent without relying on a common account ID. If the user later registers or logs in, you can link this guest session to their newly created account.

Make sure to handle session expiry and data privacy properly to avoid potential issues. This method should help with your task.

Add a comment

Write an answer...

0/9000

Jun 20, 2024, 12:52 PM

Using embeddedservice_bootstrap.utilAPI methods on an LWR site - opening a MIAW chat with an external button

I am trying to open a Messaging for In-App and Web chat programmatically, and I see that there may be some methods to do so, particularly embeddedservice_bootstrap.utilAPI methods such as:

embeddedservice_bootstrap.utilAPI.showChatButton()

The documentation shows what looks like a set up where the MIAW chat is added to a conventional website. However, I am trying to utilize these methods on an LWR site and have been unable to. Has anyone been able to pull this off? If so, how? I'm not sure what I am missing here.

#LWR

#Chat #Live Agent Web Chat #Embedded Service

5 answers

Ledwing Hernandez (Canandaigua National Bank And Trust)
Jul 2, 2024, 6:41 PM
I found the answer for this:

In order to open a MIAW chat button programmatically, in my case via a button placed elsewhere on the page, you will need to use a javascript event. To be clear, you will be using the event conventionally, not in the method described here which would be more helpful in communicating one LWC to another. The MIAW chat is not an LWC itself, but the prechat is, so that made it so that I had to use a conventional JS event.

1. Go to your desired site and drop in the Embedded Messaging component with your MIAW chat that you want to use in the Experience Builder.
2. In the left side main menu, click Settings > Advanced > Edit Head Markup.
3. In the Head Markup editor, add a simple listener like so:
document.addEventListener('launchMIAWChat', function(e){ embeddedservice_bootstrap.utilAPI.launchChat();});
4. Click Save.
5. Create an LWC that holds the button you want to use to trigger the chat.
6. Make it so that button calls a method in the LWC JS file when clicked.
7. Within the method that gets triggered on click, dispatch a JS event to the document object that has a value that matches the value your listener is listening for. Make sure to double check this since this is an easy area to make a mistake that keeps the whole thing from working:
document.dispatchEvent(new CustomEvent("launchMIAWChat"));
8. Save and deploy to the org.
9. Add the button LWC to your page.
10. You should now be able to click and have the chat open right up whether it is hidden or not.

Add a comment

Write an answer...

0/9000

Jul 24, 2024, 5:40 PM

Experience Cloud: Show Me How - How to Design Beautiful, Responsive Websites With Salesforce Experience Cloud.

Hi everyone! I'm pretty excited because I get to present my first Show Me How webinar tomorrow, July 25, at 9am PDT / 12pm EST. In this webinar I'll be showcasing a web page that was designed with Enhanced LWR Experience Builder, and demonstrating how I was able to create it. This web page was built exclusively with standard components using no custom web components, no custom HTML, and no AppExchange products. If you haven't worked with LWR very much, or are just interested to see what you can do with it, this would be a great webinar to attend.

Ask an Expert: Experience Cloud Show Me How

Date/Time: July 25 9:00 AM PDT / 12:00 PM EDT

Format: Virtual, Live Q&A

Register Here: https://cs.salesforce.com/events/7013y000002q79hAAA

Experience Cloud: Show Me How - How to Design Beautiful, Responsive Websites With Salesforce Experience Cloud. @*Experience Cloud Developers* @Salesforce.org Experience Cloud #Experience Cloud #LWR #Digital Experience

4 comments

Jason Kilp (Trifecta Technologies)
Aug 16, 2024, 6:54 PM
Hi all! I've got a followup article that was recently published on Salesforce Ben which covers some of the neat things you can do with the Columns component. The article uses the same demo website shown in the Show Me How episode, and it goes into more detail about how to achieve the layouts you see in the website.

https://www.salesforceben.com/how-to-use-salesforce-experience-builders-columns-component-like-a-pro/

If anyone has any questions about how to get similar layouts for your website, don't hesitate to reach out! I'm happy to help.