We are having problems using our webservices from Appian. It imports the WS

It means your WSDL is missing an import/include statement to reference the place where {schemas.xmlsoap.org/.../}Array is defined.

Any suggestions how to make .NET include that or point to it in a way Appian would be happy with it?

Here is an explanation msdn.microsoft.com/.../ms256237(v=vs.110).aspx

Have you done something like this yourself before? Where does this code go?

Based on the comments on this post I think you're not the owner of the web service. You need to inform the owner of the system that the generated WSDL is missing the import for schemas.xmlsoap.org/.../}Array.

If you're not familiar with the implementation of the web service, which seems to be the case, then the link I sent you won't make much sense. That said there are two options:

1. You send my first comment to the owner/developer of the web service for him to find out what the final WSDL does not include the corresponding import statement
2. You edit the WSLD to include something like this

<xs:import namespace="schemas.xmlsoap.org/.../>


*** NOTE: The syntax depends on your WSDL

Judge away, but I am the owner of the web service.
The WSDL is automatically generated by Visual Studio and we have never needed to change it manually in the past.
The line you mentioned: "<s:import namespace="schemas.xmlsoap.org/.../>" is already present in the generated WSDL.

I'm quite comfortable with the link in the article you posted. Just not really clear from the article where that code goes and how it links to the .asmx file, which is the front of the web service.

The link is just an example of what I meant by "the import element is required". I case you were not familiar with what I was saying but given you confirmed you own the web service and you generated it then you can disregard that link; you already know what I meant by importing the namespace.


I can take a look at the WSDL if you can save it and attach it here assuming there's no sensitive information there. Feel free to wipe out any server names you need to remove. I should be able to find out what's wrong with it in terms of what Appian needs. Probably some kind of inconsistency between qualified and unqualified for elements/types. I'll take a look if you attach the WSDL.

So far with the information you provided the only hypothesis I can think of is the missing import; if it's there I'll need to look at the WDL

The import was there.

We got this suggestion, that seemed to work:

Change <s:import namespace="schemas.xmlsoap.org/.../" />
To <s:import namespace="schemas.xmlsoap.org/.../" schemaLocation="schemas.xmlsoap.org/.../>

So, that change got us up and running, but ideally we would like either Appian to not require this change or Visual Studio to generate updated WSDL automatically (instead of us having to add this manually). Any idea how we can do that? It feels like we are getting close.