I have an in issue in a Summer 25 full sandbox and production on Service Cloud.
I get the following error when I try to create a new Complaint. I click on the reservation item lookup and enter an existing reservation number (ex. case : 009258614 Reservation item : 008478062)
I have to fill the case number and the order item which are lookup fields.
Once i search for it, it gives me the following error:
[Cannot destructure property 'dataType' of 'undefined' as it is undefined.] new Ce()@https://transat--preprod.sandbox.lightning.force.com/components/lightning/recordPickerCommon.js:1:11852 je.getFieldInfo()@https://transat--preprod.sandbox.lightning.force.com/components/lightning/recordPickerCommon.js:1:12909 $A.componentService.initModuleDefs.co.$A.componentService.addModule.t.ObjectInfos.getFieldInfo()@https://transat--preprod.sandbox.lightning.force.com/components/lightning/recordPickerCommon.js:1:21494 {anonymous}()@https://transat--preprod.sandbox.lightning.force.com/components/lightning/recordPickerAdvanced.js:1:8206 ee.handleObjectInfosLoaded()@https://transat--preprod.sandbox.lightning.force.com/components/lightning/recordPickerAdvanced.js:1:8157
I have verified the levels of security for every field referenced in the picker ( making them visible/invisible) I have verified the layouts/filters.
I would like to know that apart from those two, what other factors could cause lightning-record-picker to receive objectInfo.fields[] = undefined for a manages standard object (Reservation item object, the Complaint object is a custom object)? How can i isolate the exact field or metadata that the picker still expects so i can resolve this error? Also, everything was working on Friday 13th 2025. The error appeared yesterday, Monday 16th 2025. There have been no modifications since friday.