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...
Introduction:
In this blog post, we will explore how to navigate from one Lightning Web Component (LWC) to another LWC using a dynamic approach. LWC provides powerful tools and features for building interactive and responsive web components within the Salesforce ecosystem. We will cover the essential steps and provide a working code example to help you understand the navigation process. Let's dive in!
Prerequisites:
Before proceeding, make sure you have the following prerequisites in place:
- A Salesforce Developer Edition or Sandbox org
- Salesforce CLI installed and configured
- Basic knowledge of Lightning Web Components (LWC) and JavaScript
Step 1: Set Up the Salesforce Development Environment
To begin, set up your Salesforce development environment by installing Salesforce CLI and creating a project directory. You can refer to the Salesforce documentation for detailed instructions on how to set up Salesforce CLI.
Step 2: Create LWC Components
Create two LWC components using the Salesforce CLI command:
sfdx force:lightning:component:create -n firstComponent -d force-app/main/default/lwc
sfdx force:lightning:component:create -n secondComponent -d force-app/main/default/lwc
This command will create two LWC components named "firstComponent" and "secondComponent" in the specified directory.
Step 3: Define the Navigation Service
In the firstComponent, open the JavaScript file (firstComponent.js) and import the Lightning Navigation Service by adding the following line:
import { NavigationMixin } from 'lightning/navigation';
Next, include the NavigationMixin in your component's class definition:
export default class FirstComponent extends NavigationMixin(LightningElement) {
// Component code goes here
}
Step 4: Implement the Navigation Logic
Inside the class, create a method that handles the navigation to the secondComponent. Add the following code snippet:
navigateToSecondComponent() {
this[NavigationMixin.Navigate]({
type: 'standard__component',
attributes: {
componentName: 'c__secondComponent' // Replace with your secondComponent's name
}
});
}
Step 5: Add a Button to Trigger Navigation
In the firstComponent's HTML file (firstComponent.html), add a button and wire it to the navigateToSecondComponent() method. Include the following code:
<template>
<button onclick={navigateToSecondComponent}>Go to Second Component</button>
</template>
Step 6: Test the Navigation
Save your changes and deploy the components to your Salesforce org using the Salesforce CLI command:
sfdx force:source:deploy -p force-app/main/default
Once the deployment is successful, open a Salesforce Lightning App or record page that contains the firstComponent. Click the "Go to Second Component" button, and you should be navigated to the secondComponent.
Conclusion:
Congratulations! You have successfully implemented dynamic navigation from one LWC component to another. The Lightning Navigation Service in Salesforce provides a seamless way to navigate between components, improving the user experience and interactivity of your Lightning Web Components. Feel free to explore more advanced navigation options and customize the code according to your requirements. Happy coding!
Note: Remember to adjust the code snippets based on your specific component names and any additional customization you might have implemented.