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: Welcome to my blog, where I will be sharing my experience of writing my first code in Salesforce Lightning Web Components (LWC). As a Salesforce developer, I was eager to dive into LWC, a modern and efficient way to build Salesforce user interfaces. In this blog post, I will walk you through the process of creating a simple LWC component and explain the code step by step. Setting Up the Development Environment: Before we begin, make sure you have set up your Salesforce Developer Edition org and enabled the Lightning Web Components feature. You will also need a code editor such as Visual Studio Code with the Salesforce Extensions Pack installed. Creating the LWC Component: To get started, navigate to your Salesforce org and follow these steps: Step 1: Create a new Lightning Web Component: In the Salesforce setup, search for " Lightning Web Components " and click on " New ." Provide a name for your component, such as " HelloWorld ," a...