Share via


xmlFileAdapterExtension Element

Specifies the extended information for the corresponding xmlFileAdapter element in the manifest.xsf.

Usage

  
<xmlFileAdapterExtension
	ref="xsf:xdTitle"
 queryKey="xsd:string"
 queryFile="xsd:string"
/>

Element Information

Element type xsd:complexType
Namespace xsf2

Elements and Attributes

Parent Elements

Element Description
dataConnections Contains elements that specify data connections.

Child Elements

Element Description
connectoid Specifies information that describes a data connection file.

Attributes

Attribute Type Required Description Possible Values
ref xdTitle Required Specifies the name attribute of the xmlFileAdapter element that this element extends.

Note   This element or attribute is optional in the form definition file (.xsf) of a form template deployed as a browser-compatible form to a server running InfoPath Forms Services.
String
queryKey xsd:string Optional Specifies a string value generated by InfoPath and maintained in the manifest.xsf file that dictates whether the data cached in the form template at design time is applicable for the current state of the data connection.

Note   This element or attribute is optional in the form definition file (.xsf) of a form template deployed as a browser-compatible form to a server running InfoPath Forms Services.
String
queryFile xsd:string Optional Specifies the name an XML file included in the form template that contains the data cached at design time if the user selected the Store a copy of the data in the form template check box in the Data Connection Wizard. The data in the XML file will be used by Microsoft Office InfoPath if the queryKey value generated at run time matches the value stored at design time.

Note   This element or attribute is optional in the form definition file (.xsf) of a form template deployed as a browser-compatible form to a server running InfoPath Forms Services.
String
Bb265202.vs_note(en-us,office.12).gif  Note
InfoPath uses the queryKey value for all data connections that cache the query data in the form template, not only parameterized secondary data connections. This is because the data connection properties can be changed by business logic code at run time. For example, a secondary ADO query connection's connection string can be changed at run time, so the queryKey value is necessary to validate the applicability of the cached data. Similarly, the URL for a Web service or XML document query data connection can be changed from code at run time.

Definition

  
<xsd:element name="xmlFileAdapterExtension">
   <xsd:complexType>
      <xsd:sequence>
         <xsd:element ref="xsf2:connectoid" minOccurs="0" />
      </xsd:sequence>
      <xsd:attribute name="ref" type="xsf:xdTitle" use="required" />
      <xsd:attributeGroup ref="xsf2:queryKeyFile" />
   </xsd:complexType>
</xsd:element>

Remarks

InfoPath adds the xmlFileAdapterExtension element to the manifest.xsf file when an XML document data connection is defined using one or more of the following features:

  • The Store a copy of the data in the form template check box is selected in the Data Connection Wizard.
  • The data connection settings are specified from from a data connection file (.udcx) in a data connection library.

Note   This element or attribute is optional in the form definition file (.xsf) of a form template deployed as a browser-compatible form to a server running InfoPath Forms Services.

Example

The following is an example of the xmlFileAdapterExtension element.

  
<xsf2:xmlFileAdapterExtension ref="ScenarioFindings" queryKey="C:\Example\ScenarioFindings.xmlScenarioFindings" queryFile="ScenarioFindings_offline.xml"></xsf2:xmlFileAdapterExtension>