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) and Lightning Message Service provide developers with a powerful combination to implement the publish-subscribe (pub-sub) pattern within the Salesforce platform. This pattern allows components to communicate and exchange data efficiently, enabling seamless coordination and collaboration between different parts of an application. In this blog post, we will explore the concept of the pub-sub pattern and delve into how to leverage Lightning Message Service to implement it in Salesforce LWC. 1. Understanding the Publish-Subscribe Pattern: The publish-subscribe pattern is a messaging paradigm where components or modules can act as publishers or subscribers. Publishers send messages (events) containing data, while subscribers listen for specific events and respond accordingly. This decoupled approach enables loose coupling between components and promotes reusability, scalability, and flexibility in application design. 2. Introduci...