refresh LWC page when editing or created a related record

Question

On the Account record page, I want to refresh my LWC page whenever I create or edit a related contact record. My LWC page is fetching list records from apex not using LDS.

I couldn't think of any way to achieve the same so I thought of wrapping my LWC in the aura and use the below aura code.

<aura:component implements="flexipage:availableForRecordHome">
    <aura:handler name="init" value="{!this}" action="{!c.doInit}" />

    <aura:dependency resource="markup://force:editRecord" type="EVENT" />

    <aura:handler event="force:refreshView" action="{!c.doInit}" />
</aura:component>

JS:

doInit: function (component, event, helper) {
    console.log('from aura');
},

I get a console log when I edit the account record but don't get anything when I edit the contact record from the related list of account.

is there any way I can detect if a record is created or updated from the related list either in lwc or aura?

Answer 1

You should be able to run your imperative Apex call from a getRecord adapter:

import { LightningElement, api, wire } from 'lwc';
import { getRecord } from 'lightning/uiRecordApi';
import { refreshApex } from '@salesforce/apex';
import myMethod from '@salesforce/apex/MyClass.myMethod';

export default class MyLWC extends LightningElement {
    @api recordId;
    result;
    
    @wire(getRecord, { recordId: '$recordId', fields: ['Account.Id'] })
    getRecordData({ error, data }) {
        if (this.recordId) {
            refreshApex(this.result);
            this.imperativeApexFunction();
        }
    }
}

imperativeApexFunction() {
    myMethod({ recordId: this.recordId })
        .then( result => {
            console.log(result);
            this.result = result;
            // Handle result
        })
        .catch( error => {
            console.log(error);
            // Handle error
        })
}

The @wire getRecord adapter is intrinsically connected to the LDS, and will automatically run when a change is saved to the parent record, or a related child record, causing your Apex method to rerun as well

The recordId is not always set by default on page load, and it is helpful to include a check to see if there is a recordId before running your Apex method to prevent null errors