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 Dynamic Working Code for Navigation Service in Salesforce Lightning Web Component (LWC)

Introduction:

In Salesforce Lightning Web Components (LWC), the Navigation Service is a powerful tool that enables seamless navigation between different pages and components within an application. With the Navigation Service, you can build dynamic and interactive user experiences. In this blog post, we will explore how to implement full dynamic working code for the Navigation Service in LWC. So, let's dive in!


Prerequisites:


Before we begin, make sure you have the following prerequisites in place:

  1. Salesforce Developer Account or Org.
  2. Basic understanding of Lightning Web Components (LWC).
  3. Salesforce CLI (Command Line Interface) installed and set up.
  4. Knowledge of JavaScript, HTML, and CSS.

Step 1: Setting Up the Project


To start, create a new Lightning Web Component project using the Salesforce CLI. Open your terminal or command prompt and execute the following command:


sfdx force:project:create -n lwc-navigation-demo

cd lwc-navigation-demo


Step 2: Create a Lightning Web Component


Now, let's create a new Lightning Web Component called "NavigationDemo." Run the following command in your terminal:


sfdx force:lightning:component:create -n NavigationDemo -d force-app/main/default/lwc


Step 3: Implementing the Navigation Logic


Open the "NavigationDemo" component folder and navigate to the JavaScript file "NavigationDemo.js." Replace the existing code with the following:


import { LightningElement } from 'lwc';

import { NavigationMixin } from 'lightning/navigation';


export default class NavigationDemo extends NavigationMixin(LightningElement) {

  handleNavigation() {

    this[NavigationMixin.Navigate]({

      type: 'standard__recordPage',

      attributes: {

        recordId: '001XXXXXXXXXXXXXXX',

        objectApiName: 'Account',

        actionName: 'view'

      }

    });

  }

}


In the code above, we import the NavigationMixin from the 'lightning/navigation' module and extend it in our component. The handleNavigation() function is responsible for triggering the navigation.


Step 4: Creating the User Interface


Open the HTML file "NavigationDemo" in the same component folder and replace the existing code with the following:


<template>

  <lightning-button label="Navigate to Account" onclick={handleNavigation}></lightning-button>

</template>


The code above creates a simple UI with a Lightning button that triggers the handleNavigation() function when clicked.


Step 5: Deploy and Test the Component


To deploy and test the component, run the following commands in your terminal:


sfdx force:source:push

sfdx force:org:open


This deploys the component to your Salesforce org and opens it in a new browser tab.


Step 6: Test the Navigation


In the Salesforce org, locate and add the "NavigationDemo" component to a Lightning page or record page layout. Save the changes, and you should see the button labeled "Navigate to Account." Clicking this button triggers the navigation and takes you to the Account record page.


Conclusion:


Congratulations! You have successfully implemented a full dynamic working code for the Navigation Service in Lightning Web Components (LWC) in Salesforce. The Navigation Service opens up a wide range of possibilities for building interactive and seamless user experiences within your Salesforce applications. Feel free to explore more features and options provided by the Navigation Service and enhance your LWC applications further. 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.