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...
Lifecycle Flow in LWC: A Guide to Understanding the Salesforce Lightning Web Component Lifecycle with Example Code
Introduction: Salesforce Lightning Web Components (LWC) have revolutionized the way developers build user interfaces on the Salesforce platform. LWC provides a powerful framework for creating reusable, performant, and modern web components. As a developer, understanding the lifecycle flow of an LWC is crucial for building robust and efficient applications. In this blog post, we will explore the lifecycle flow of an LWC and provide example code to demonstrate each stage. 1. Creation Stage: The first stage in the lifecycle flow of an LWC is the creation stage. During this stage, the component is initialized, and its constructor is called. Any necessary setup can be performed in the constructor, such as initializing variables or setting default property values. Here's an example of the creation stage: