I am trying to pass a value from one component (Component A) in a lightning app (Home page) to another component (Component B) in a different lightning app (App page). The components are not parent/child, and the components are not within one container. Therefore, they are two independent components.

When a link is clicked on Component A, a value is supposed to be passed to the application event then the user is directed to Component B, which is supposed to handle and show the passed value. On the first click, I am redirected to Component B but the value does not appear. However, when I return to the Home page and click on the link again, I am directed to Component B but this time the value appears!

How do I get the value to appear on the first click?

The dispatching component markup, componentA.cmp:

<aura:component implements="flexipage:availableForAllPageTypes">
    <aura:registerEvent name="passTheValue" type="c:ApprovalDashboardStatus"/>
        <lightning:navigation aura:id="navService"/>
        <a name="theValueToPass" onclick="{!c.handleClick"}">Click Me</a>

The dispatching controller, componentAController.js:

handleClick : function(component, event, helper) {
    var setEvent = $A.get("e.c:passTheValueEvent");
        "valueToPass": event.currentTarget.name;

    var evt = $A.get("e.force:navigateToComponent");
        componentDef : "c:componentB"

The application event, passTheValueEvent.evt:

<aura:event type="APPLICATION">
    <aura:attribute name="valueToPass" type="String" />

The receiving component's markup, componentB.comp:

<aura:component implements="flexipage:availableForAllPageTypes, lightning:isUrlAddressable" controller="lightningUtils">
    <aura:handler event="c:passTheValueEvent" action="{!c.getTheValue}"  />

The receiving component's controller, componentBController.js:

getTheValue : function(component, event, helper) {
    var receiveTheValue = event.getParam("valueToPass");

The value is not passed initially on the first click. However, when I return to Component A and click again, the value is passed that time. How do I make the value pass on the first click?

2 Answers 2


You have declared

But not using it. Check out below link Component Navigation

force:navigateToComponent is old and soon to be a deprecated way of component navigation

Using the new pageReference type you won't need to even use the event as you can pass the attribute directly to component B and read it in its controller.

The reason you are not able to read the value in the first click is due to the event not being fired by Component A by the time you navigated to the component B.

  • Thank you for this! I was able to use this method to get the value on the first click. Now I have a different issue. After the first click, when I go back to the Home page and change the value, clicking on the link again navigates to Component B, but Component B only shows the value from the first click. The second time it does not refresh with the new value. How do I make Component B update/refresh with every click?
    – Jay
    Commented May 14, 2019 at 15:13
  • Never mind, I got it working! Thanks so much for your help!
    – Jay
    Commented May 14, 2019 at 18:58

Thanks maniac coder, I was able to accomplish this task. Instead of using an application event, I used pageReference which allows me to both send values and navigate to the second component.

Additional info: Clicking on Component A's link allows me to navigate to Component B's page and handle the passed value using the pageReference method. However, going back to the Home page, updating the value, and clicking on the link again redirects you to Component B, but the value is not refreshed and the data from the first click remains. To solve this, I used the fix from this post.

<aura:handler name="change" value="{!v.pageReference}" action="{!c.reInit}"/>

In short, a change handler for the pageReference state and a reInit function was added. Then, I made the reInit function call the getTheValue function. The change handler does not fire on initial load. It fires on re-navigation to the component.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .