Adding data connection from webservice

[Schroeder@discussions.microsoft.com Steve Schroeder]

While the error I am getting is rather general and non specific, I am getting
a Type Mismatch error when trying to add a new connection from a web service.
Are there any typical problems associated with this error, things to check?
Thank you.

[S.Y.M. Wong-A-Ton]

Perhaps the type of web service you're trying to add a data connection for is
not supported? See http://msdn.microsoft.com/en-us/library/bb852081.aspx for
more information.
---
S.Y.M. Wong-A-Ton
http://www.bizsupportonline.net (100+ InfoPath articles, tutorials, and
solutions)

[Zamdrist]

On Jan 3, 1:27 am, S.Y.M. Wong-A-Ton
<SYMWongA...@discussions.microsoft.com> wrote:
> Perhaps thetypeofwebserviceyou're trying to add a data connection for is

> not supported? Seehttp://msdn.microsoft.com/en-us/library/bb852081.aspxfor
> more information.
> ---

> S.Y.M. Wong-A-Tonhttp://www.bizsupportonline.net(100+ InfoPath articles, tutorials, and
> solutions)
>

Well, I'm adding a secondary data connection from an existing WSDL
file that I know previously worked. The vendor should be able to help
with the problem yet. I was told I had to manually add a complex type
to the WSDL file, which I did. I've re-double-checked the syntax and
second-guessed myself numerous times now. I'm not terribly familiar
with the format and syntax, though I have examples to work off of. The
'type mismatch' error to me at least alludes to a data type issue
issue more than anything. I know if I have a malformed WSDL file I get
a whole different message. So, I don't think I'm missing a quote or
bracket somewhere that I can see.

[S.Y.M. Wong-A-Ton]

If you have Visual Studio, you could try creating a project with a connection
to that WSDL and see whether it works. If not, the issue is not with the data
connection in InfoPath, but with the WSDL.
---
S.Y.M. Wong-A-Ton

"Zamdrist" wrote:

> .
>

[Zamdrist]

On Jan 4, 8:35 pm, S.Y.M. Wong-A-Ton

<SYMWongA...@discussions.microsoft.com> wrote:
> If you have Visual Studio, you could try creating a project with a connection
> to that WSDL and see whether it works. If not, the issue is not with the data
> connection in InfoPath, but with the WSDL.

Turned out to be an irrelevant or erroneous line inserted into the
WSDL file by the company's proprietary IDE

<import schemaLocation=".../MG_Template.xsd" /> *Edited for security*

After that line was removed and the file saved, InfoPath had no issues
reading the file. All along my syntax was correct, a complex type I
added. Frustrating.