Article ID: 889494 - Last Review: April 17, 2007 - Revision: 2.1

InfoPath 2007 and InfoPath 2003 cannot correctly generate a form when a WSDL file uses definitions with a type reference

Expand all | Collapse all

SYMPTOMS

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"

CAUSE

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.

RESOLUTION

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.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

APPLIES TO
  • Microsoft Office InfoPath 2007
  • Microsoft Office InfoPath 2003, Service Pack 1 (SP1)
  • Microsoft Office InfoPath 2003
Keywords: 
kbpending kbprogramming kbtshoot kbbug KB889494
 

Article Translations

 

Related Support Centers