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 powerful framework for building modern, dynamic user interfaces within the Salesforce platform. One of the key aspects of developing robust LWC applications is efficient component communication. In this blog post, we will explore various techniques and best practices for effectively communicating between LWC components, enabling seamless data sharing and collaboration. 1. Parent-to-Child Component Communication: One common scenario in LWC development is passing data from a parent component to a child component. This can be achieved by leveraging properties or attributes. The parent component sets the values of properties or attributes, which are then accessed by the child component. This approach enables data sharing and ensures that child components have access to the necessary data for rendering. 2. Child-to-Parent Component Communication: Conversely, there are situations where a child component needs to communi...