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 Lightning Web Components (LWC) have revolutionized the way we develop Salesforce applications. They provide a modern and efficient approach to building user interfaces in the Salesforce ecosystem. One of the key features that make LWC so powerful is its event system. In this blog post, we will delve into LWC events, exploring how they work and the benefits they offer. Understanding LWC Events Events in LWC follow a publish-subscribe pattern, where components can communicate with each other by firing and handling events. This decoupled communication model enables loose coupling between components, promoting reusability and flexibility. There are two types of events in LWC: standard events and custom events. 1. Standard Events: LWC provides a set of standard events that components can use out-of-the-box. These events are defined by the framework and are available for use in various scenarios. Examples of standard events include 'click', 'change', 'sub...