Are You Supplying all the mandatory Fields to Create WO?
I'd done a test in SOAP UI with a set of fields populated and the test was successful. So, I used the same set of fields in the .NET project, but got the above error.
Is there a standard set of required fields? My understanding is that the required fields are implementation specific.
in your xml structure(wsdl)
check if namespace parameter is defined properly?
targetNamespace="urn:HPD_IncidentInterface_Create_WS" it should ideally be matching the name of the web service that exists in your remedy midtier server(you can find your list http://midtierservername:8080/arsys/WSDL/protected/list )
namespace="http://tempuri.org"/ (not null right?)
1 of 1 people found this helpful
take a look at this document, although related to Incident (and somewhat an old document) the principles are the same:
Web Services act differently to normal API calls, so you have to supply more fields than you would when using the API.
The Work Order Interface form is somewhat a "pain" compared with the other application interface forms i.e. the required fields are not properly defined as they are on say the Incident interface. Best to manually attempt a submission and then once working move to your WS.
If you are programming a .NET interface, I would recommend using the .NET API wrapper as opposed to the Web Services - it offers more flexibility as is multi-threaded and does not require the same overhead as Web Services.
I was able to figure out the issue. I'd copied the web service URL straight out of the WSDL when configuring the integration and it had '&' encoded in it:
This was the value being set for the URL property of the derived class from SoapHttpClientProtocol. I removed the encoding in the URL and replaced it with just the '&' character which made the error go away.
Thanks for chiming in everyone!