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:
The session ID is a crucial piece of information when working with Salesforce, as it grants access to the platform's various functionalities and APIs. In this guide, we will walk you through the step-by-step process of obtaining the session ID in Salesforce. By following these instructions, you'll be equipped with the knowledge to seamlessly integrate your applications with Salesforce and leverage its powerful features. Let's get started!
Step 1: Utilizing the POST Method
To begin, we need to use the POST method, which allows us to send a request to Salesforce's authentication endpoint. This request will contain the necessary information for logging in and retrieving the session ID.
Step 2: Setting the Endpoint
Depending on whether you are working in a sandbox or production environment, you will need to set the appropriate endpoint URL. For a sandbox, the URL should be set to:
- Sandbox: https://test.salesforce.com/services/Soap/u/55.0
- Production: https://login.salesforce.com/services/Soap/u/55.0
Step 3: Configuring Headers
To ensure a successful request, we need to set the appropriate headers. There are two headers that need to be configured:
- SOAPAction: Set this value to an empty string.
- Content-Type: Set this value to "text/xml".
Step 4: Constructing the Request Body
The request body contains the login information required to authenticate and retrieve the session ID. Use the following XML structure as the body of your request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:partner.soap.sforce.com">
<soapenv:Body>
<urn:login>
<urn:username>Login ID</urn:username>
<urn:password>Password</urn:password>
</urn:login>
</soapenv:Body>
</soapenv:Envelope>
Replace "Login ID" with your Salesforce login username and "Password" with your corresponding password with security token. This information will be used to authenticate and generate the session ID.
Step 5: Retrieving the Session ID
Once the request is sent, Salesforce will respond with the session ID. This ID is a unique identifier that grants access to Salesforce resources for a specific user. Capture and store the session ID for future use in your Salesforce integration or application.
Conclusion:
Obtaining the session ID in Salesforce is a fundamental step in working with the platform's APIs and integrating external applications. By following the steps outlined in this guide, you can easily retrieve the session ID and unlock the full potential of Salesforce. Harness the power of Salesforce's features and streamline your business processes with confidence.