Open letti2017 opened 1 week ago
This is an issue with a Lightning Component, not the LWC framework (this repo). To resolve your issue, I would recommend opening a Salesforce Stack Exchange question or a Salesforce case.
I will raise a case as well, just wanted to get as many eyes on this as possible since it's causing our team a lot of problems with rendering based on the event.detail.record
object that comes back from onLoad
Updating records outside of standard LDS wires might be picking up cached values. LDS Consideration Docs
https://developer.salesforce.com/docs/component-library/bundle/lightning-record-edit-form/documentation The "load" section goes into detail what causes the onload to trigger. Posting on Stack Exchange might be able to offer additional support how to get latest data.
Updating records outside of standard LDS wires might be picking up cached values. LDS Consideration Docs
https://developer.salesforce.com/docs/component-library/bundle/lightning-record-edit-form/documentation The "load" section goes into detail what causes the onload to trigger. Posting on Stack Exchange might be able to offer additional support how to get latest data.
I must be missing something then, because based on my understanding of the documentation provided here, the onLoad
function will fire when LDS has updates to the record from the system.
However, I've noticed that without changing any of the values on the record, either on the server or within the lwc itself, the event.detail.record
still does not contain the most up-to-date information somewhat randomly.
Description
Steps to Reproduce
lightning-record-edit-form
with arecordId
,recordTypeId
, andobject-api-name
filled out with an existing recordlightning-input-field
with any fields on the specific objectonLoad
function provided forlightning-record-edit-form
, then access theevent.detail.record
object that is returned, which should consistently have the list of fields (i.e.event.detail.record.fields
) for the record specified in thelightning-record-edit-form
event.detail.record.fields
should consistently have the most up-to-date information on the fields provided inlightning-record-edit-form
and should only fire onceExpected Results
onLoad
function in the above example only fires once and contains the most up-to-date information on the record provided in the html.Actual Results
onLoad
is fired inconsistently and may not contain the most up-to-date information, which can cause issues when using theevent.detail.record
to run specific rendering rules based on the values provided for the record.Browsers Affected
All Browsers, all versions.
Version