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...
Building Components in Mixed Shadow Mode in Salesforce Lightning Web Components (LWC): A Guide for Developers
Introduction: Salesforce Lightning Web Components (LWC) is a modern framework for building web applications on the Salesforce platform. LWC allows developers to create reusable, efficient, and scalable components that can be used across different Salesforce applications. One of the powerful features of LWC is the ability to use the mixed shadow mode, which provides a unique way to combine the best of both the shadow DOM and the traditional DOM models. In this blog post, we will explore the concept of mixed shadow mode in LWC and discuss how to build components using this mode. What is Mixed Shadow Mode in LWC?