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: Salesforce Lightning Web Components (LWC) provide a modern, lightweight framework for building custom user interfaces in Salesforce. One important concept to grasp when working with LWC is the Light DOM, which refers to the way components handle and manipulate their child elements. In this blog post, we will delve into the concept of Light DOM in LWC and provide code examples to help you understand it better. What is Light DOM? The Light DOM in LWC represents the component's immediate child elements within its template. These child elements are directly defined in the component's markup. The Light DOM is responsible for displaying content and interacting with the component's JavaScript and CSS. Understanding Light DOM Hierarchy: