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: As a Salesforce developer, it's essential to have effective debugging tools at your disposal. The Developer Console in Salesforce provides powerful features to assist in identifying and resolving issues within your code. In this blog post, we will explore two essential tools within the Developer Console: Checkpoints and Assertions. These tools can significantly aid in the debugging process, allowing you to validate assumptions, track variable values, and identify problematic areas in your code. Table of Contents: 1. Introduction 2. The Salesforce Developer Console 3. Understanding Checkpoints a. Setting Checkpoints b. Inspecting Variable Values 4. Leveraging Assertions a. Defining Assertions b. Verifying Assumptions 5. Enhancing Debugging with Logs 6. Conclusion