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 Components are a powerful framework within Salesforce that allows developers to build interactive and dynamic user interfaces. One key aspect of Lightning Components is their execution modes, which determine how the components are rendered and interact with the underlying data. In this blog post, we will explore the various execution modes available in Lightning Components and discuss their advantages and use cases. 1. Introduction to Execution Modes: Execution modes in Lightning Components refer to the different ways in which the components can operate. These modes provide developers with flexibility and control over how their components function and interact with the Salesforce platform. The three main execution modes are: