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: Salesforce provides powerful integration capabilities, allowing you to receive JSON payloads through a SOAP web service and seamlessly insert the data into your Salesforce org. In this blog post, we will explore how to write Apex code to receive a JSON payload and use it to insert records into Salesforce using a SOAP web service. Step 1: Define the SOAP Web Service Endpoint and Request To receive the JSON payload, you need to define a SOAP web service endpoint and create a corresponding request in Salesforce. This can be achieved by creating a global Apex class with a web service method decorated with the @WebService annotation. The method should accept a JSON payload as a string parameter.