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: Working with large datasets in Salesforce often requires efficient ways to retrieve specific records based on predefined criteria. One powerful feature Salesforce offers is List Views, which allow users to define custom views that filter and display records based on specified conditions. In this blog post, we will explore how to leverage Apex code to fetch records using List View IDs. By implementing this approach, you can streamline your record retrieval process and optimize data management within your Salesforce org. Let's dive in! Step 1: Obtain the List View ID: The first step is to identify the List View from which you want to fetch records. Navigate to the desired List View in Salesforce and extract its unique ID. This ID is required to reference the specific List View in the Apex code. Step 2: Create an Apex Class: Next, create a new Apex class in Salesforce to encapsulate the functionality of fetching records by List View ID. Begin by defining the class and e...