Skip to main content

Latest Post

Custom Metadata Types vs Custom Settings vs Custom Labels

  Custom Metadata Types vs Custom Settings vs Custom Labels 💬 In plain words:  Three lookalikes: Custom Metadata = configuration that DEPLOYS with your code (best for app settings). Custom Settings = org/user-specific values, changeable at runtime (hierarchy type is great for bypass switches). Custom Labels = translatable text for the UI. 📌 Example:  API endpoint URLs per environment → Custom Metadata (deploys with code, sandbox vs prod values). A 'Bypass_Automation__c' checkbox an admin flips during data load → hierarchy Custom Setting. The word 'Submit' translated to Hindi → Custom Label. 🎬 Real-Life Example: The Fee Table Trapped Inside Code  Skyline charges a different delivery fee per city. Apex needs those rates on every booking. The Old/Bad Way:  if (city == 'Delhi') fee = 50. Else if (city == 'Mumbai') fee = 65. … Every rate change is a code change, a test run, and a deployment. Why this is bad:  Business data is trappe...

LWC Full Code with Output Screen for Navigating to an Aura Component from LWC

Introduction:

In this blog post, we will explore how to navigate from a Lightning Web Component (LWC) to an Aura Component in Salesforce. We will provide a step-by-step guide along with the full code and an output screen to help you understand the process. By the end of this blog, you will be able to implement navigation from an LWC to an Aura Component seamlessly. So, let's get started!


Prerequisites:


To follow along with this tutorial, make sure you have the following prerequisites:

  1. Salesforce Developer Account or Sandbox
  2. Salesforce CLI
  3. Basic knowledge of LWC and Aura Components

Step 1: Create the Aura Component


First, let's create the Aura Component that we will navigate to from the LWC. Open your Salesforce CLI and navigate to the desired directory. Use the following command to generate the Aura Component:


sfdx force:lightning:component:create -n AuraComponentName -d aura


This command will create the Aura Component files in the "aura" directory with the specified name. You can replace "AuraComponentName" with your preferred name.


Step 2: Implement the Aura Component


Next, open the generated Aura Component files in your preferred code editor. Modify the AuraComponentName.cmp file with the following code:


<aura:component>

  <h1>This is the Aura Component</h1>

</aura:component>


Save the changes and deploy the Aura Component using the Salesforce CLI:


sfdx force:source:deploy -p aura/AuraComponentName


Step 3: Create the LWC


Now, let's create the Lightning Web Component from where we will navigate to the Aura Component. Use the following command in your Salesforce CLI:


sfdx force:lightning:component:create -n LWCComponentName -d lwc


Replace "LWCComponentName" with your preferred name.


Step 4: Implement the LWC


Open the generated LWC files in your code editor. Modify the LWCComponentName.js file with the following code:


import { LightningElement } from 'lwc';


export default class LWCComponentName extends LightningElement {

  navigateToAuraComponent() {

    const event = new CustomEvent('navigate', {

      detail: {

        component: 'c:AuraComponentName'

      }

    });

    this.dispatchEvent(event);

  }

}


Next, modify the LWCComponentName file with the following code:


<template>

  <h1>This is the LWC Component</h1>

  <button onclick={navigateToAuraComponent}>Navigate to Aura Component</button>

</template>


Save the changes.


Step 5: Add the LWC to a Page


To see the output of the LWC and test the navigation to the Aura Component, add the LWC to a Lightning page. Open the Salesforce CLI and use the following command to create a Lightning page:


sfdx force:lightning:app:page:create -n MyLightningPage -t LWCComponentName


Replace "MyLightningPage" with your preferred name.


Step 6: Assign the Lightning Page to a Lightning Experience App


Next, assign the Lightning page to a Lightning Experience App. Use the following command in the Salesforce CLI:


sfdx force:lightning:app:assign -p MyLightningPage -a YourApp


Replace "MyLightningPage" with the name of the Lightning page you created, and "YourApp" with the name of the Lightning Experience App you want to assign the page to.


Step 7: Verify the Output


Open your Salesforce Developer Account or Sandbox and navigate to the assigned Lightning Experience App. You should see the LWC with the "Navigate to Aura Component" button. Click the button, and it will navigate you to the Aura Component. You should see the output on the screen displaying the text "This is the Aura Component."


Conclusion:


Congratulations! You have successfully learned how to navigate from an LWC to an Aura Component in Salesforce. By following the steps outlined in this blog post, you were able to create an Aura Component, implement navigation logic in an LWC, and test the output on the screen. With this knowledge, you can enhance your Salesforce applications by seamlessly navigating between Lightning Web Components and Aura Components. Happy coding!

Popular Posts

Salesforce LWC Code for Multi-Select Lookup

Introduction: In Salesforce Lightning Web Components (LWC), implementing a multi-select lookup field can enhance the user experience and provide greater flexibility for selecting multiple related records. In this blog post, we will walk through the process of creating a multi-select lookup field using LWC. We will cover the required code snippets and provide step-by-step instructions to help you implement this functionality in your Salesforce org.