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 Aura Components are powerful tools that allow developers to create dynamic and interactive user interfaces within the Salesforce platform. To enable seamless integration and collaboration between LWC and Aura Components, Salesforce provides the capability to communicate between these components using Aura Events. In this blog post, we will explore how LWC and Aura Components can communicate effectively through Aura Events, enabling developers to build robust and interconnected applications. 1. Understanding Aura Events: Aura Events serve as a communication mechanism between Lightning Web Components and Aura Components. They allow for the exchange of data, triggering actions, and broadcasting events across components. Aura Events follow a publish-subscribe pattern, where a component publishes an event and other components that subscribe to the event can receive and respond to it. 2. Publishing Aura Events from LWC Components: L...