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) empower developers to build modern and efficient user interfaces on the Salesforce platform. With their modular architecture, reusability, and enhanced performance, LWCs have become a preferred choice for creating seamless user experiences. In this blog post, we present a handy LWC cheatsheet that will accelerate your development process, provide quick reference points, and unlock productivity in your Salesforce projects. 1. Component Basics: Creating a Lightning Web Component: Use the @api decorator to expose properties and methods for communication between components. Component Lifecycle Hooks: Leverage lifecycle hooks like connectedCallback() , renderedCallback() , and disconnectedCallback () to handle component initialization, rendering, and cleanup.