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: In the world of Salesforce development, accessing and manipulating data is a crucial aspect of building robust and efficient applications. Traditionally, developers relied on Apex code and custom queries to interact with data. However, with the introduction of Lightning Data Service (LDS), Salesforce offers a declarative way to work with data, reducing the need for custom code and enhancing developer productivity. In this blog post, we'll explore Lightning Data Service and provide code examples to demonstrate its power and ease of use.