Hello Everyone! I'm having an issue with Record Edit Forms when using them to create a record.
We have an sObject where we are using a LWC as the overloaded 'New' button. Since Input Fields don't allow us to create related records in line like we can in the Native Salesforce experience I've gone ahead and created a custom lookup component with that 'Create New Record' button that will open up a modal and based on the object's schema build a form from the fields on the page layout.
This was working great for a while, but recently we have been seeing a component error crop up that looks like this:
[NoErrorObjectAvailable] Script error.
{anonymous}()@https://static.lightning.force.com/cs92/auraFW/javascript/Q8onN6EmJyGRC51_NSPc2A/aura_prod.js:955:389
dispatchEvent()@https://static.lightning.force.com/cs92/auraFW/javascript/Q8onN6EmJyGRC51_NSPc2A/aura_prod.js:12:33511
I.dispatchEvent()@https://static.lightning.force.com/cs92/auraFW/javascript/Q8onN6EmJyGRC51_NSPc2A/aura_prod.js:12:7816
o.createOrSaveRecord.then._pendingAction()@https://java-customer-5018-dev-ed.lightning.force.com/components/interop/recordEditForm.js:1:7223
The record is successfully created and the rest of our code runs to completion, but this annoying grey popup still shows up.
I've stripped this component down to it's bare roots (Just the record edit form) without any custom functions and I'm still having the same results. You can see the Stripped version below.
<lightning-record-edit-form object-api-name="Account">
<lightning-input-field field-name="LastName"></lightning-input-field>
<lightning-button type="submit" label="submit"></lightning-button>
</lightning-record-edit-form>
My THOUGHTS are that this error is happening in Salesforce' managed code and it is presenting itself due to the fact that we are creating records on a record create page for a completely different sObject.
One final note, I've tried using the Record Form component have have had success. The only reason I want to use the Record Edit Form is it will respect the page sections.
Thanks!
Our issue is likely nowhere near related to the OP's, but for future travelers who happen upon this question in a desperate grasp at straws (like I did):
We have custom LWCs embedded in a custom Aura component that (in some sandboxes) suddenly had Component Errors that look a lot like the OP's.
After much weeping and gnashing of teeth, we discovered that Salesforce had gone into our Session Settings and checked "Enable Content Delivery Network (CDN) for Lightning Component framework." Upon disabling (unchecking), the Component Error went away.
Knowledge Article 005115596 (
https://help.salesforce.com/s/articleView?id=005115596&type=1), titled, "Salesforce Lightning CDN Preference Auto Enablement" and which as of this writing is showing published 31 July 2025, states, "As this only impacts Salesforce owned content, we are enabling the org preference to be ON for customers that have the preference set to OFF. There is no required action that needs to be taken as this will be enabled by Salesforce."
I filed a Support Case, and in it said that I want to refute the "this only impacts Salesforce owned content" statement.
