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: Salesforce Apex, the programming language used in Salesforce, enforces certain limits to ensure efficient resource allocation and prevent abuse. These limits, known as Governor Limits, govern the amount of resources like CPU time, heap size, database queries, and more that Apex code can consume. It's crucial for Salesforce developers to understand these limits and handle potential Governor Limit Exceptions appropriately. In this blog post, we will explore common Governor Limit Exceptions in Salesforce Apex and discuss best practices to handle them. Table of Contents: 1. Introduction 2. What are Governor Limits? 3. Common Governor Limit Exceptions a. CPU Time Limit Exceeded b. Heap Size Limit Exceeded c. Too Many SOQL Queries d. Too Many DML Statements e. Concurrent Request Limit Exceeded 4. Best Practices for Handling Governor Limit Exceptions a. Efficient Code Design and Optimizatio...