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: Batch processing is a powerful feature in Salesforce that allows you to efficiently process large volumes of data in chunks. In this blog post, we will explore the concept of batch processing, its benefits, and provide code examples to demonstrate how to implement a batch class in Salesforce. What is Batch Processing? Batch processing is a technique used to process a large amount of data in smaller, manageable chunks. It breaks down a large job into multiple smaller jobs called batches, which are processed sequentially. This approach is particularly useful when dealing with large datasets that would otherwise exceed governor limits in a single execution.