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, efficient debugging is essential to identify and resolve issues in your Apex code. Salesforce provides a powerful tool called the Apex Debugger, which allows you to step through your code, inspect variables, and analyze the flow of execution. In this blog post, we'll explore the Apex Debugger and learn how to leverage its features to streamline the debugging process in Salesforce. Table of Contents: 1. Introduction 2. What is the Apex Debugger? 3. Enabling the Apex Debugger 4. Setting Breakpoints 5. Stepping Through Code 6. Inspecting Variables 7. Using Debug Logs 8. Best Practices for Effective Debugging 9. Conclusion What is the Apex Debugger? The Apex Debugger is a tool provided by Salesforce that allows developers to interactively debug Apex code. It provides a controlled environment to step through code execution, pause at breakpoints, inspect variables, and gain insights into the flow of the program. The Apex Debugger is...