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
somasoma 

webservice callout causing XML document error

1. Is there a newer method of calling out to web services from javascript other than through remoteFunction()?

 

2. During an attempt to access a web service being hosted outside Salesforce by means of remoteFunction(), I'm seeing a confusing parameter being referenced as the culprit of an error:

 

 

Internal Server Error:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <soap:Body>
      <soap:Fault>
         <faultcode>soap:Client</faultcode>
         <faultstring>Server was unable to read request. ---&gt; There is an error in XML document (46, 27). ---&gt; Value cannot be null.

Parameter name: dest</faultstring>
         <detail />
      </soap:Fault>
   </soap:Body>
</soap:Envelope>
 
 Neither
in the SOAP message I'm constructing to communicate with the web
service nor in expected parameters outlined in the WSDL for my web
service is there a parameter named "dest." Here's an example of an
outgoing SOAP message this error applies to:
 
 
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:xsd="http://www.w3.org/2001/XMLSchema"
	xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
	<soap:Body>
		<Send xmlns="http://my.webservices.com/">
			<token>97ed86a3970b48e3887b6978c600f048</token>
			<meetingId>Meet-002104</meetingId>
			<toEmailAddresses>
			</toEmailAddresses>
			<bccEmailAddresses>
			</bccEmailAddresses>
			<participants>
				<EmailParticipants>
					<EmailAddress>cgarrett@p4healthcare.com</EmailAddress>
					<ParticipantDetails>
						<ParticipantInfo>
			    				<Id>a0YS000000065WwMAI</Id>
				    			<Name>Chris1 Garrett</Name>
					    		<Type>Physician</Type>
				    		</ParticipantInfo>
						<ParticipantInfo>
			    				<Id>a0YS000000065WxMAI</Id>
				    			<Name>Chris2 Garrett</Name>
					    		<Type>Physician</Type>
				    		</ParticipantInfo>
						<ParticipantInfo>
			    				<Id>a0YS000000065X1MAI</Id>
				    			<Name>Chris3 Garrett</Name>
					    		<Type>Physician</Type>
				    		</ParticipantInfo>
						<ParticipantInfo>
			    				<Id>a0YS000000065X6MAI</Id>
				    			<Name>Chris4 Garrett</Name>
					    		<Type>Physician</Type>
				    		</ParticipantInfo>
						<ParticipantInfo>
			    				<Id>a0YS000000065X7MAI</Id>
				    			<Name>Chris5 Garrett</Name>
					    		<Type>Physician</Type>
				    		</ParticipantInfo>
						<ParticipantInfo>
			    				<Id>a0YS000000065X8MAI</Id>
				    			<Name>Chris6 Garrett</Name>
					    		<Type>Physician</Type>
				    		</ParticipantInfo>
					</ParticipantDetails>
				</EmailParticipants>
			</participants>
			<fromEmailAddress>cgarrett@p4healthcare.com</fromEmailAddress>
			<subject>this is a test; do not reply</subject>
			<body>test message</body>
			<useHtml>true</useHtml>
		</Send>
	</soap:Body>
</soap:Envelope>
 
 Notice
the supposed null parameter mentioned in the error message is on line
46, character 27 of this SOAP message. That doesn't quite make sense,
as that particular position references the '>' character of
"</ParticipantDetails>".
 
Any suggestions?