Navigating to record detail page after edit does not reflect new data

Question

After we update a record and navigate to a detail page, it still shows the old data.

Steps:

• Overridden edit button of Account with a Lightning component.
• Also used a Visualforce page with lightning out to host the component as an override, but still have same issue.

---

Note: Navigation issue is in 2 places:

1. Lightning Component: Using e.force:navigateToSObject
2. Visualforce using lightning out: sforce.one.navigateToSObject

It looks like there is some caching issue after redirect.

---

To resolve this, I also turned off the cache as mentioned in this question, it didn't help: Lightning Experience: How to prevent the display of obsolete data?

Question is similar to Values are not updated in Lightning after record update but it does not have a proper answer.

I also know there is a known issue: Data updates are not reflected in UI after a Visualforce+Apex update in Lightning Experience. My scenario is different as it has a lightning component.

Please let me know if anyone else is facing similar issue; as this is most common use case to use a Lightning component or Visualforce for overriding standard button's action.

My code is pretty basic to just show the existing Account name with save button, can provide if required.

---

What I tried for navigation:

Iteration 1:

var navigationSObject = $A.get("e.force:navigateToSObject");
navigationSObject.setParams({
    "recordId": component.get("v.recordId")
});
navigationSObject.fire();

And using sforce.one.navigateToSObject when a VF page is used using Lightning out.

---

Iteration 2 (as per question: Values are not updated in Lightning after record update):

var navigationSObject = $A.get("e.force:navigateToSObject");
navigationSObject.setParams({
    "recordId": component.get("v.recordId")
});
$A.get('e.force:refreshView').fire();
navigationSObject.fire();

Answer 1

Used window.location as mentioned in the comments which opens the salesforce app inside child container/page.

Finally ended up using window.parent.location as below (instead of using $A.get("e.force:navigateToSObject") or sforce.one.navigateToSObject for Lightning component or VF page respectively.) -

window.parent.location = '/' + recordId;

Not sure if this is completely supported by Lightning but works for now.

---

Added:

1. Tested and this works in Lightning UI when standard button is overridden:

   • Directly with Lightning component
   • Indirectly via Visualforce using Lightning out
   • When component is used in app builder.

2. I have disabled toast message, showing a success message via toast is weird as message appears following by redirection.

Answer 2

I found other workaround without redirection.

Adding an empty Lightning component for the affected layout:

Component code:

<aura:component implements="flexipage:availableForAllPageTypes"  access="global">
    <aura:handler name="init" value="{!this}" action="{!c.handleInit}"/>
</aura:component>

Controller code:

({
    handleInit : function(component, event, helper) {
        setTimeout(function(){ 
            $A.get('e.force:refreshView').fire();
        }, 1);


    }
})

In this case when you use "e.force:navigateToSObject" the layout is refreshed.

Answer 3

I have experienced a similar situation with an Aura component and Lightning Data Service. The issue was that we use a custom Apex controller to save the record. Lightning Data Service does not get notice about the change in database. It is not meant to be used that way, I think. One should use Lightning Data service to save the record.

However, I found a solution here: https://salesforce.stackexchange.com/a/249233/76507

Call reloadData(true) on your Lightning Record Service component to reload the record from the server.

    saveRecord: function(component, event, helper) {
        // call Apex controller
        var action = component.get("c.saveRecord");
        action.setParams({
            recordId: component.get("v.recordId"),
            recordFields: JSON.stringify(fields)
        });
        action.setCallback(this, function(response) {
            if(response.getState() === "SUCCESS"){
                // tell Lightning data service to reload record from server
                component.find("recordLoader").reloadRecord(true);
                // navigate to record page
                helper.navToRecord(component, response.getReturnValue().recordId);               

            } else {
                helper.handleError(component, response);
            }
        });
        $A.enqueueAction(action);
    },