function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Yohann ChevreuxYohann Chevreux 

Enterprise WSDL upsert definition with webmethods

Hi,

i'm facing a problem with the Enterprise WSDL and the definition of the upsert method.
Importing WSDL in webmethods (it's also true with SOAPUI), the generated upsert request does not contain the attribute "type" in the sObjects element.
The generated request is as follow:
<soapenv:Body>
      <urn:upsert>
         <urn:externalIDFieldName>?</urn:externalIDFieldName>
         <!--Zero or more repetitions:-->
         <urn:sObjects>
            <!--Zero or more repetitions:-->
            <urn1:fieldsToNull>?</urn1:fieldsToNull>
            <urn1:Id>?</urn1:Id>
         </urn:sObjects>
      </urn:upsert>
   </soapenv:Body>

And what webmethods is expected is:
<soapenv:Body>
      <urn:upsert>
         <urn:externalIDFieldName>?</urn:externalIDFieldName>
         <!--Zero or more repetitions:-->
         <urn:sObjects type="?">
            <!--Zero or more repetitions:-->
            <urn1:fieldsToNull>?</urn1:fieldsToNull>
            <urn1:Id>?</urn1:Id>
         </urn:sObjects>
      </urn:upsert>
   </soapenv:Body>

As the way webmethods is used, point and click generated callouts, we cannot modify callout adding the type attribute to the sObjects element.
Has anyone ever experienced such a problem?
Has someone an idea for a workaround?
 
ShashankShashank (Salesforce Developers) 
The generated request is just a sample. We wiill have to manually add the type to be able to make the calls successfully. I am not well versed with webmethods, but this is what we do in SOAPUI. Here's a sample: https://developer.salesforce.com/page/Enterprise_Upsert