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: Integrating Google Search Address API with Salesforce allows you to leverage the power of Google's address search capabilities within your Salesforce applications. By implementing the API in Apex code, you can streamline address validation, enhance data accuracy, and provide a seamless user experience. In this blog post, we will delve into the Apex code required to integrate the Google Search Address API into your Salesforce org. Let's get started! Step 1: Obtain API Key from Google: To utilize the Google Search Address API, you first need to obtain an API key from the Google Cloud Platform. This key will authenticate your requests to the API and enable access to its features. Follow Google's documentation to create and configure an API key specific to your Salesforce org. Step 2: Set Up Apex Class: Create a new Apex class in Salesforce to encapsulate the functionality of the Google Search Address API integration. This class will handle the API request, proce...