SOAP Integration in Salesforce

If you don’t know the basics of SOAP fear not, because I've got you covered! Dive into the basics of SOAP with my latest blog, 'SOAP Explained: With JavaScript.’

Oh, you already know about SOAP and are here to learn how it works in Salesforce? You've come to the right spot! Let's get started.


SOAP Integration in Salesforce

SOAP is a protocol where client and server are tightly coupled meaning that minor changes on either side can potentially disrupt the connection. 


To use SOAP API, your org must use Enterprise Edition, Performance Edition, Unlimited Edition, or Developer Edition. In all supported editions, a user must have the API Enabled permission turned on in the user profile they’re assigned. 


In Salesforce, Apex SOAP web services(It is like a class) allow an external application to invoke Apex methods through SOAP Web services. The Web service that is available to you is defined in generated WSDL file.


What is WSDL?

Web Service Description Language is a file that defines all of the API calls, objects (including standard and custom objects), and fields that are available for API access for your organisation.


Salesforce provides two SOAP API WSDLs for two different use cases. 

  1. Enterprise WSDL
  2. Partner WSDL
Enterprise WSDL

This API is mainly for people in big companies who are creating applications for their organisation.

The enterprise WSDL file is a strongly typed, It provides information about your schema, data types, and fields to your development environment, allowing for a tighter integration between it and the Lightning Platform Web service.


NOTE: This WSDL changes if custom fields or custom objects are added to, renamed, or removed from, your org’s Salesforce configuration.


Partner WSDL

This API is designed for Salesforce partners who are building applications for use across multiple organisations. The partner WSDL file is loosely-typed representation of the Salesforce object model, can be used to access data within any org.


Use Case: Typically, if you’re writing an integration for a single Salesforce org, use the enterprise WSDL. For several orgs, use the partner WSDL.


How to generate API WSDL file for org

Step1: Go to Setup, search for api


Step2: Generate wsdl file 


Generate Apex Classes in external salesforce org

You can use the above-generated WSDL file to integrate an external system using any other language, such as Java, or you can use it to produce Apex classes in Salesforce (org which wants to communicate with source org’s SOAP API). 

I've included an example at last of how these Apex classes will be used to access the SOAP API.





How to create SOAP web service in Source Salesforce org?

Use the webservice keyword to define Apex class methods to expose it as custom SOAP Web service. This allows an external application to invoke an Apex Web service to perform an action in Salesforce. See the following example:

global class SOAPWebService {
	// SOAP Webservice
	webservice static Id createContact(String contactLastName, String email) {
		Contact c = new Contact(lastName = contactLastName, email = email);
		insert c;
		return c.id;
	}
}


Note: When you use a custom webservice method, it always uses system context, not the current user's credentials. This means any user accessing these methods can have full control, regardless of their individual permissions. Developers should be careful not to accidentally expose sensitive data through these methods.

How to generate WSDL file for Class?

This WSDL file will be used


1. Setup > Apex Classes


2. Click on your class that contains web service method

3. Click Generate WSDL

You can create a soap callout now that you have developed the SOAP API in the source org and all the necessary classes in the external salesforce org.


Example of how to do SOAP callout in external salesforce org:

partnerSoapSforceCom.Soap myPartnerSoap = new partnerSoapSforceCom.Soap();

partnerSoapSforceCom.LoginResult partnerLoginResult = myPartnerSoap.login(
    <userName>, 
    <Password>+<SecurityToken>
); 

soapSforceComSchemasClassSoapwebser.SessionHeader_element webserviceSessionHeader = 
    new soapSforceComSchemasClassSoapwebser.SessionHeader_element();

webserviceSessionHeader.sessionId = partnerLoginResult.sessionId;

soapSforceComSchemasClassSoapwebser.SOAPWebService myWebservice = 
    new soapSforceComSchemasClassSoapwebser.SOAPWebService(); 

myWebservice.SessionHeader = webserviceSessionHeader; 
myWebservice.createContact('Ambani', 'mukesh@fakegmail.com');


Comments

Post a Comment

Popular posts from this blog

How to Add a Dynamic Child List to Parent in Apex Class || Trigger using map

Last Updated: 13-01-2024 Map<parentId, List<child>>  Code without comments Map<id, List<object>> parentIdAndChildRecordsMap = new Map<id, List<object>>(); for(object childRecord : Trigger) { if(parentIdAndChildRecordsMap.containsKey(childRecord.parentId__c)) { parentIdAndChildRecordsMap.get(childRecord.parentId__c).add(childRecord); } else { parentIdAndChildRecordsMap.put( childRecord.parentId__c, new List<object>{childRecord} ); } } Code with comments // Define a map to store parent IDs and their associated child records Map<id, List<object>> parentIdAndChildRecordsMap = new Map<id, List<object>>(); // Iterate through each object in the Trigger context (likely a trigger context variable) for(object childRecord : Trigger) { // Check if the map already contains the parent ID if(parentIdAndChildRecordsMap.containsKey(childRecord.parentId__c)) { // Parent ID found, so add the child record to the existin
Read more

A - Z Guide to Using the Wire Decorator in LWC Salesforce

Image
Certainly! In Salesforce Lightning Web Components, the "wire service" is a feature that brings data to your component. Imagine this data as a never-ending river of information, and each piece of information in this river is like an updated version of the one before it. What's special is that once you receive a piece of data, it's like taking a snapshot in time; you can't change it. Instead, as new data becomes available, it replaces the previous one in the stream. This way, your component always has the latest and most up-to-date information without you having to constantly ask for updates. It's like having a continuous flow of fresh data at your fingertips. Syntax // Wire to a property @wire (methodName, {parameterName: '$value'}) result; // Wire to a function @wire (methodName, {parameterName : value}) callbackFtn(result) { const {data, error} = result; if(data) { // Add logic }   else if(error) {} } When you should use wire to function when
Read more

(Salesforce Apex 2024 Release) getSalesforceBaseUrl method is deprecated

Image
  The getSalesforceBaseUrl() method is no longer available and deprecated in API versions 59.0 and beyond. Alternatively, use getCurrentRequestUrl() to obtain the URL of a complete request on a Salesforce instance, or getOrgDomainUrl() to obtain your organization's URL. A compilation error occurs when the deprecated method in API version 59.0 and later is attempted to be used. System.debug(URL.getOrgDomainUrl());
Read more