This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Hi,
How have others handled the fact that XML data flows may or may not include the same or a fixed set of elements in them. So you have no idea what will need processing from delivery to the next?
Does anyone have examples of returning a success/failure value as an output value from a stored procedure to the snap. The following is not visible in the output view of my sproc snap:
Return(@Status)
…Never mind, it’s working now…just a little too i...
Any help much appreciated in this regard in terms of sample envelopes you can share or validated WSDL, currently using v28.1 which doesn’t validate in XMLSpy although it seems to work with SOAPUI
Yours,
Adrian
Trying to execute a SOAP web service request against workday and getting the following:
An exception occurred while executing the SOAP request
Resolution
Verify that the template is correct, the substituted values are valid and the provided envelope ...
Anyone managed to get this to work using dynamic values i.e.
‘MyFileName’ +data.now()+‘.txt’
plus does anyone know how to cause this to fail if the file never turns up?
Currently it seems to finish with success no matter what.
OMG - I had a capital 'A’rriva3 in the tenant field arriva3 now validates and I can see the available methods.
case sensitivity aaaargh! - case conversion as feature request please
For the workday snap using a workday account I’m getting:
Cannot Parse WSDL
Resolution
Please verify account settings and retry
Reason
Server returned HTTP response code: 500 for URL: https://wd3-impl-services1.workday.com/ccx/service/Arriva3/Absence...
Ok just checked and the tenant is not being patched and is available through other means, but still getting the following when executing the SOAP Execute using WSSE security:
An exception occurred while executing the SOAP request
Resolution
Verify th...
Thanks for the help and the prompt response…and yes 28.1 not v28.1 in the workday snap.
I had crossed my wires, thought you were referring to the URL for the WSDL in the soap snap.
Ok I’ve switched the SOAP snap to use WSSE instead of basic authentic...
Thanks for confirming the host, wasn’t sure upto what point on the url it mattered.
BTW - /v28.1?WSDL appears to be the correct way to reference it, it’s working at any rate in the SOAP execute snap, without it I get an invalid request service versio...
