We have a Lightning Out form that sits on a public website using embed code. The component uses Apex to define the form and create records when the form is submitted. The Apex has a method which reads custom metadata settings so that they can be presented on a section of the form and included with the form submission.

Until the Summer 23 update, this has been working fine. Since the update, the main form still loads, so the Apex isn't broken. However it fails to load the element obtained from the custom metadata settings on the form page. We assume therefore that the Apex isn't fundamentally broken but that for some reason it is no longer able to read the custom metadata settings.

Troubleshooting has been extensive so far, including checks on Apex class permissions, Custom Metadata permission settings, Experience site settings, Experience site guest user profile permissions, Debug log etc.

Wondering if anyone else has come across a similar issue?

Hi All!

I've got a Live Agent question:

We have a use case where we want to have chats started from a couple pages on our site to route to a different team, while the majority of chats on the site goes to the general chat queue. This part we were able to achieve with deploying a different chat button on those pages which routes to that other team. On that front, everything works well.

The issue we're finding though is some of our customers are moving from page-to-page while in a chat. If they go from a page where we have this secondary chat button deployed to one with the primary chat button, we lose connection with that customer.

I guess the question is: is there any way that we can maintain the chat when users navigate to a primary chat page? Maybe some way to deploy the secondary chat on a primary page so that it's hidden, but will allow customers coming from a secondary chat page to maintain their current chat?

What is upsert? How it works?