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: In Salesforce, there are various ways to upload files and attachments. One common requirement is to upload files using the multipart/form data format. This format allows you to send file data along with additional form parameters in a single request. In this blog post, we'll explore how to accomplish this using Apex code in Salesforce. Prerequisites: Before diving into the implementation, make sure you have the following prerequisites in place: Salesforce Developer Edition or Sandbox account. Basic knowledge of Apex programming language. Salesforce org with the necessary permissions to create Apex classes and Visualforce pages.