You may have a Web Service Description Language (WSDL) file for a Web service that uses definitions with the following attributes:
| • | A type attribute that is similar to the following:
<message name="GetReturnXmlNodeSoapOut">
<part name="XmlNoder" type="s0:myType" />
</message> |
| • | An element attribute that is similar to the following:
<message name="GetReturnXmlNodeSoapOut">
<part name="parameters" element="s0:GetReturnXmlNodeResponse" />
</message>
|
With this WSDL file, Microsoft Office InfoPath 2007 and Microsoft Office InfoPath 2003 cannot correctly generate a form from the Web service method, and you may receive an error message that is similar to the following:
"/schema/element[1][@name='myFields']/complexType[1]/sequence[1]/element[2]
[@name='dataFields']/complexType[1]/sequence[1]/element[1]
Undeclared XSD element: {http://tempuri.org/}XmlNoder"
Back to the top
This problem occurs because InfoPath does not generate the correct XSD code when a part has a type reference. SOAP returns an empty
Message name value.
Back to the top
Microsoft regularly releases software updates to address specific problems. If Microsoft releases a software update to resolve this problem, this article will be updated with additional information.
Back to the top
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
Back to the top
Help and Support
