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 modern and efficient way to build user interfaces on the Salesforce platform. As you dive into LWC development, mastering component communication becomes crucial to create interactive and cohesive user experiences. In this blog post, we will explore the concept of parent-to-child component communication in LWC and discuss effective strategies to achieve seamless data flow and interaction between components. 1. Understanding Parent-to-Child Component Relationship: In LWC, parent and child components interact through a hierarchical relationship. The parent component encapsulates one or more child components and can pass data and properties down the component tree. This allows for a structured and modular approach to building complex user interfaces. 2. Utilizing Properties for Data Transfer: One of the primary ways to establish communication between parent and child components is through properties. The parent compone...