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) offer a powerful way to build web applications on the Salesforce platform. One fundamental concept to grasp when working with LWC is the concept of the Light DOM. In this blog post, we will explain what the Light DOM is and how it functions within LWC, providing you with a clear understanding of its purpose and usage. Understanding the Light DOM: The Light DOM, short for " Light Document Object Model, " is a core concept in web development that LWC leverages. It refers to the hierarchy of HTML elements and their relationships within a component. In simpler terms, the Light DOM represents the structure and content of an LWC component's template.