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...
Salesforce Custom Events for Cross-Component Communication: Enhancing Collaboration and Extensibility
Introduction: In Salesforce, building complex applications often involves multiple components working together to deliver a cohesive user experience. To facilitate seamless communication and collaboration between these components, Salesforce introduced Custom Events. Custom Events enable cross-component communication, allowing developers to create loosely coupled and highly extensible applications. In this blog post, we will explore the concept of Salesforce Custom Events and how they enhance collaboration and extensibility within the Salesforce platform. 1. Understanding Custom Events: Custom Events in Salesforce provide a standardized mechanism for communication between components. They allow components to publish and subscribe to specific events, enabling them to exchange information, trigger actions, and synchronize their behavior. 2. Loose Coupling and Modularity: By utilizing Custom Events, developers can decouple components from one another, promoting modularity and code ...