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: When writing unit tests in Salesforce, having reliable and relevant test data is crucial for comprehensive testing and accurate validation of your code. The Test Data Factory class provides a powerful solution for generating test data in a structured and efficient manner. In this blog post, we will explore the concept of a Test Data Factory class and discuss how it can simplify and streamline your unit testing process in Salesforce. Let's get started! What is a Test Data Factory Class? A Test Data Factory class is a utility class designed to generate test data programmatically. It encapsulates the logic for creating test records, setting field values, and establishing relationships between objects. The Test Data Factory class acts as a centralized hub for generating consistent and reusable test data across multiple test classes. Benefits of Using a Test Data Factory Class: 1. Standardized Data Generation: The Test Data Factory class ensures consistent and standardize...