This documentation is archived and is not being maintained.

viewExtension Element

Office 2007

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

Usage


<viewExtension
	ref="xsf:xdTitle"
	designMode="xsd:string"
	readOnly="xsf:xdYesNo"
	clientOnly="xsf:xdYesNo"
/>

Element Information

Element type xsd:complexType
Namespace xsf2

Elements and Attributes

Parent Elements

ElementDescription
viewsExtensionContains viewExtension elements that specify extended information for the views in this form template.

Child Elements

ElementDescription
xmlToEditExtensionSpecifies the extended information for the xmlToEdit element in the manifest.xsf whose name attribute matches the ref attribute of this element.

Attributes

AttributeTypeRequiredDescriptionPossible Values
refxdTitleRequiredSpecifies the name of the existing view element in the manifest.xsf 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
designModexsd:stringOptionalSpecifies whether the view contains controls that are not supported in Microsoft Office InfoPath 2003 and will be prevented ("protected") from being edited in InfoPath Design mode in that release of InfoPath.

In Office InfoPath 2007, if you perform any of the following actions, InfoPath sets the value of the designMode attribute for the view element that contains these items to "protected":

  • Insert a Combo Box control.
  • Insert a Multiple Selection List Box control.
  • Insert a Combo Box, Drop-Down List Box, or List Box control, and then select the Show only entries with unique display names check box on the Data tab of the control's Properties dialog box.
  • Enable digital signatures for data in a Section control.

Additionally, when you perform one of these actions, InfoPath also sets the value of the designMode attribute for the viewExtension element to "normal". This prevents the view from being edited in Design mode if the form template is opened in InfoPath 2003, but still allows it to be edited in Design mode when the form template is opened in Office InfoPath 2007. If you want to prevent the view from being edited in both InfoPath 2003 and Office InfoPath 2007, then you must manually edit the manifest.xsf file for the form template and change the value of the designMode attribute for the viewExtension element to "protected".
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.
  • normal
  • protected
readOnlyxdYesNoOptionalSpecifies whether the view is a read-only view.

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.
  • yes
  • no
clientOnlyxdYesNoOptionalSpecifies whether the view has features that will work only when the form template is opened in InfoPath, and whether the view should not be exposed if the form template is opened in a Web browser from a server running InfoPath Forms Services.
  • yes
  • no

Definition


<xsd:element name="viewExtension">
   <xsd:complexType>
      <xsd:sequence>
         <xsd:element ref="xsf2:xmlToEditExtension" minOccurs="0" maxOccurs="unbounded" />
      </xsd:sequence>
      <xsd:attribute name="ref" type="xsf:xdTitle" use="required" />
      <xsd:attribute name="designMode" type="xsd:string" use="optional" />
      <xsd:attribute name="readOnly" type="xsf:xdYesNo" use="optional" />
      <xsd:attribute name="clientOnly" type="xsf:xdYesNo" use="optional" default="no"/>
      <xsd:anyAttribute  processContents="skip" />
   </xsd:complexType>
</xsd:element>

Remarks

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.



Show: