Contents
How to create an account using SOAP API and SoapUI?
I logged in through SOAPUI and used the session id to create an account. The account gets created and returns success. However when I try to validate the challenge in trailhead, it gives me an error – It doesn’t appear that you have logged in using SoapUI. I am not sure what did I miss out. Please consider below points.
Why is my login not working with SoapUI?
It doesn’t appear that you have logged in using SoapUI. Which was odd, as I’d explicitly performed the login and create calls via Soap UI. In my case I found the problem was with the org itself.
Is there a problem with the SOAP API challenge?
The only problem is with the SOAP API challenge where it is giving me a specific error message even though I logged into SOAPUI, used the sessionid that I received from the Login () request and used it to create Account Records successfully. The records get created but the challenge isn’t getting validated.
How to create a soap account in Salesforce?
I am doing this trailhead ( https://trailhead.salesforce.com/modules/api_basics/units/api_basics_soap) and done everything whatevet mention in this and i got success message that account is created but when i click on the check & challenge button it’s showing error message
How to find out what version of Java SOAP uses?
You can find out information about the version of Java that SoapUI uses by selecting Help | System Settings from within SoapUI. After you get SoapUI installed and launched, from the File menu, select New SOAP Project. For the project name, enter Exploring Salesforce SOAP API.
Where do I find the SOAP API in Salesforce?
After you get SoapUI installed and launched, from the File menu, select New SOAP Project. For the project name, enter Exploring Salesforce SOAP API. For the initial WSDL, browse to where you saved the enterprise WSDL file and select it.
How to add a new end point to a SOAP request?
To resolve this issue you need to add a new end point to your SOAP request in SoapUI. Use the URL present in element in the Login response. This will fix your issue. The problem is not with the actual request, but with the URL that you’re sending the request to.