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?

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?

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?