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: Dynamic variables play a crucial role in Salesforce development when it comes to building flexible and adaptable solutions. In Apex, dynamic variables empower developers to construct dynamic SOQL (Salesforce Object Query Language) queries, enabling the retrieval of records based on varying conditions at runtime. In this blog post, we will explore the code implementation of dynamic variables in SOQL queries using Apex Salesforce. By leveraging this approach, you can enhance the flexibility and scalability of your code to meet evolving business requirements. Let's dive in! Step 1: Identify Query Criteria: Begin by identifying the criteria or filters that need to be dynamic in your SOQL query. These criteria can be based on user inputs, runtime conditions, or any other dynamic factors that impact the query's results. Step 2: Declare Dynamic Variables: In your Apex code, declare the necessary dynamic variables. These variables will hold the values that will be dynami...