[SalesForce] Data not returned by wire service

I am unable to get data using getRecord method if wired to a function. The same call work when it is wired to property. I have given the code below. When wired to function, error and data (in wiredAccount function) are coming back as undefined.

Wired to method (not working)

@wire(getRecord, { recordId: '$clientId', fields: accountFields })
wiredAccount({ error, data }) {
    console.log('in wiredAccount');
    if (data) {
        this.account = data;
        this.error = undefined;
    } else if (error) {
        this.error = error;
        this.account = undefined;
    }
}

Wired to property (working)

@wire(getRecord, { recordId: '$clientId', fields:accountFields })
account;

Best Answer

The wire service first provisions the shape of the value: { data: undefined, error: undefined }. This enables wiring of properties and their direct use in the template to test for data and error. Eg <template if:true={wiredProperty.data}>.

This is why you see said value provided to your wired function.

As for why it's not being invoked a second time with the data or error, I recommend checking the values of this.clientId and this.accountFields. Are either undefined? Per https://developer.salesforce.com/docs/component-library/documentation/lwc/data_wire_service_about, Properties in the adapterConfig object can’t be undefined. If a property is undefined, the wire service doesn’t provision data. Try setting a breakpoint (eg with debugger) in connectedCallback() and inspecting the values.

Related Solutions

Lightning Web Components – Fixing Undefined recordId in Spring ’20

After further testing, it turns out that the optionalFields property is more restrictive in the update. If an optional field is listed when not looking at the correct record type, it will prevent the wired method from running again when the recordId is updated. In our case, we use the component in both the Case page and Contact page. We had one wire/getRecord method that listed optionalFields for both the Case and Contact record types. After removing the contact fields, the components began loading correctly on the Case page.

To remedy the issue, for now, two separate wire methods were created. One for the Contact page and the other for the Case page.

Old Code:

@wire(getRecord, {
    recordId: "$recordId",
    optionalFields: [
        "Contact.Name",
        "Case.Contact.Name"
    ]
})

New Code:

@wire(getRecord, {
    recordId: "$recordId",
    optionalFields: [
        "Contact.Name"
    ]
})

@wire(getRecord, {
    recordId: "$recordId",
    optionalFields: [
        "Case.Contact.Name"
    ]
})

Lightning Web Components – How to Call LWC Wire Adapters Imperatively

No, wire methods cannot be called imperatively.

Use Apex in these scenarios:

...

To call a method imperatively, as opposed to via the wire service. You may want to call a method imperatively in response to clicking a button, or to delay loading to outside the critical path. When you call an Apex method imperatively, to refresh the data, invoke the Apex method again.

If you need to do some special handling afterwards, set this up in the wire handler:

@wire(method, params) 
 wireHandler({data,error}) {
  if(data) {
   this.handleData(data);
  }
  if(error) {
   this.handleError(error);
  }
 }

To actually trigger the call, you can set a reactive variable:

someVariable;
@wire(method, {param:'$someVariable'})

If you wanted to further make the call dynamic, you can do that, too!

someVariable;
someCallback;
@wire(method, {param:'$someVariable'}) 
 wireHandler({data,error}) {
  if(data) {
   this.someCallback(data);
  }
  if(error) {
   this.handleError(error);
  }
 }
 handleClick(event) {
  this.someCallback = (result) => {
   console.log(result);
  };
  this.someVariable = 'Hello World';
 }

Wired to method (not working)

Best Answer

Related Solutions

Lightning Web Components – Fixing Undefined recordId in Spring ’20

Lightning Web Components – How to Call LWC Wire Adapters Imperatively

Related Topic