AdrianH
New Contributor II
Joined 9 years ago
User Profile
User Widgets
Contributions
SQL Stored Procedures - Output Parameters
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 impatient perhaps 😉1.8KViews0likes0CommentsRe: Anyone got a SOAP Execute against a Workday Tenant Working?
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_Management/v28.1?wsdl but the url resolves in a browser window - This is a Show Stopper Right Now!. <?xml version="1.0" encoding="UTF-8"?> -<wsdl:service name=“Absence_ManagementService”> -<wsdl:port name=“Absence_Management” binding=“wd-wsdl:Absence_ManagementBinding”> <soapbind:address location=“https://wd3-impl-services1.workday.com/ccx/service/arriva3/Absence_Management/v28.1”/> </wsdl:port> </wsdl:service> </wsdl:definitions>889Views0likes0CommentsRe: Anyone got a SOAP Execute against a Workday Tenant Working?
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 the input data is correct Reason tenant is temporarily unavailable due to server patching1.9KViews0likes3CommentsRe: Anyone got a SOAP Execute against a Workday Tenant Working?
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 authentication and now I’m getting tenant not available due to patching notification so not good but not bad On the workday snap front getting the following when pressing the validate button: failure: Cannot connect to the endpoint reason: Server returned HTTP response code: 500 for URL: https://wd3-impl-services1.workday.com/ccx/service/Arriva3/Integrations/v28.1?wsdl resolution: Please file a defect against the snap Thought this should be validating against the following instead: https://wd3-impl-services1.workday.com/ccx/service/Arriva3/v28.1?wsdl Not sure how …integrations… snuck in.1.9KViews0likes0CommentsRe: Anyone got a SOAP Execute against a Workday Tenant Working?
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 version error or content not allowed in prolog error. Still be unable to connect with SOAP or Workday snap different issues. In the case of the workday snap it’s trying to resolve against the following URL instead of the one above: https://wd3-impl-services1.workday.com/ccx/service/integrations/Human_Resources/v28.1?wsdl don’t know why, so any ideas most welcome. Unable to workout why I’m getting invalid username/password errors, works for me in SOAPUI so the credentials aren’t the issue must be missing something just don’t know what at this point.1.4KViews0likes1CommentRe: Anyone got a SOAP Execute against a Workday Tenant Working?
Never mind just spotted the extra space in the url, now I’m getting this: Failure: Cannot Parse WSDL, Reason: Content is not allowed in prolog., Resolution: Please file a defect against the snap So a couple of questions for you: Which tenant are you using? What security credentials are you using? Yours, Adrian1.5KViews0likes0Comments