Lightning New Case action override

Question

I have action override on New Case button which runs our custom component. As you know, we can create a new Case from different places in org, e.g. from related lists. When creating a Case from related list on Account using standard action in Lightning we have prepopulated AccountId to the lookup field. Is it possible to do the same with custom component? I can't catch the AccountId using force:hasRecordId, because action override redirects me to the new page with custom component where I don't have a context of Account. URL also doesn't contain its Id. What can I do to grab Id of context object and populate it to my component?

Answer 1

There is a solution that does indeed work, but it's a bit fragile because it's parsing the entire URL (assuming a structure that could change): https://developer.salesforce.com/forums/?id=9060G000000UaqdQAC (look at Pascal Le Clech's answer).

However, we can build on this idea and make it more structurally sound by using https://developer.salesforce.com/docs/component-library/bundle/lightning:isUrlAddressable to grab the new inContextOfRef which gives us a URL Addressable Base 64 encoded string. Here's a slightly more stable solution to Pascal Le Clech's solution:

aura:component

<aura:component implements="lightning:actionOverride, force:hasRecordId, lightning:isUrlAddressable">
    <aura:attribute name="recordId" type="Id"/>
    <aura:handler name="init" value="this" action="{!c.init}"/>
</aura:component>

controller.js

({
    init : function(cmp, event, helper) {
        var pageRef = cmp.get("v.pageReference");
        var state = pageRef.state; // state holds any query params
        var base64Context = state.inContextOfRef;

        // For some reason, the string starts with "1.", if somebody knows why,
        // this solution could be better generalized.
        if (base64Context.startsWith("1\.")) {
            base64Context = base64Context.substring(2);
        }
        var addressableContext = JSON.parse(window.atob(base64Context));
        cmp.set("v.recordId", addressableContext.attributes.recordId);
    }
})

Answer 2

As of today, you cannot capture the "parent context" on a lightning component invoked from a related list. We have had a similar situation and found out that it is not possible and ended up creating this idea requesting for a feature around this.

The alternative that we came up was to create a custom button on the parent record itself and then create the related list records. We invoked the same component that was invoked from related list, but were able to pass the parent context in this case. While this worked for the use case that we had, but it may be necessarily true in your case, but this is one of the options you can try.

Answer 3

If your use case permits, another solution might be to use sessionStorage. Aside from your custom action override component, you will need one additional component.

CaseOverride.cmp - your custom "New Case" form, which you assign to the New override for Case. This is the one where you currently can't get the Account Id for a new Case.

CaseOverrideHelper.cmp - a component you place in the Account Lightning page. It has one job: to capture the Account recordId and store it in a session variable.

Each time your Account Lightning page loads, your session variable will be updated with the current Account Id and available to your New Case action override component, and any other component that needs it.

CaseOverrideHelper.cmp

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

CaseOverrideHelperController.js

({
    doInit : function(component, event, helper) {
        // Get Account ID and place in storage
        sessionStorage.setItem("accountId", component.get("v.recordId"));
    }
      
})

Now, in your custom "New Case" override component (CaseOverride.cmp), you can retrieve the Account ID in the controller or helper like this:

    var accountId = sessionStorage.getItem("accountId");

Answer 4

I am also stuck with same thing

google below link which is working fine for me you can also try this

hope this work for you

click here