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 working with Salesforce metadata deployments, retrieving the package.xml file is a crucial step. Traditionally, developers have relied on tools like Workbench to generate the package.xml file. However, there are alternative methods available that can simplify the process and offer more flexibility. In this blog post, we will explore different approaches to obtain the package.xml file without relying on Workbench. 1. Salesforce CLI: Salesforce CLI (Command Line Interface) provides a powerful command-line toolset for Salesforce development and deployment. Using Salesforce CLI, you can retrieve the package.xml file by executing the following command in your command-line interface: sfdx force:source:retrieve -x path/to/package.xml This command retrieves the metadata specified in the package.xml file and downloads it to your local machine. Salesforce CLI offers enhanced flexibility and automation capabilities compared to Workbench, making it a preferred choice for...