Show All

# About XML Schema improvements

Many improvements have been made for XML Schema (.xsd) support in Microsoft Office InfoPath 2003 Service Pack 1.

Native support for the following XML Schema constructs have been added to InfoPath:

- Abstract types
- Abstract elements and substitution groups
- Required wildcard (<any>)
- Repeating or optional model groups in the schema (sequence, choice, group, and all with minOccurs or maxOccurs different from 1)
- Inline schemas

## Interactive incremental creation of the data source

To support abstract types or elements and required wildcards, creation of the data source is now interactive. For example, schema creation is not possible if the schema delegates part of its syntax to other schemas. This can happen when a type or an element is defined as abstract or when the content model of an element contains an <any>. When one of these conditions occurs, InfoPath will prompt the user to specify a schema source that contains the needed data before proceeding. This process is repeated until the schema collection that is loaded contains enough information to generate a complete data source.

## Better model group support

Model groups specified as "choice" or "sequence" and with minOccurs or maxOccurs not equal to 1 are now shown in the Data Source task pane. They can be bound to controls, and they can be treated as a group in the data source.

Note Model groups designated as "group" or "all" are not displayed in the Data Source task pane.

## Native support for inline schemas

Inline schemas are natively supported during design. This feature allows you to use an XML document that contains its own schema as a data source.

## Support for data source change

The underlying data structure of a form can now be changed during form creation. Clicking Convert Main Data Source on the Tools menu allows you to convert the current data source while retaining the information that depends on it.

Changing a data source is restricted to the following paths:

- Converting from a blank form, XML Schema, or XML file to another XML Schema or XML file.
- Converting from a Web service or other data connection to another Web service or data connection.

Once you specify the new data source, all dependent data will be mapped to the new data source. If the data cannot be mapped, controls will appear unbound in the view.

Note Changing the data source does not update the code associated with the form. Also, after using the Convert Main Data Source command, you cannot use the Undo command on the Edit menu to revert to the original data source.

## Recursive template support

The Repeating Recursive Section control adds recursive structures of arbitrary depth to a form.

This control is now the default control when you drag a recursive structure from the Data Source task pane.

The properties of the recursive section correspond to the properties of an ordinary section, with the exception that digital signatures are not allowed. The only property that can be set in the internal recursive block is the default value of the XML fragment for additional recursive sections inserted within the outermost instance.

©2003-2004 Microsoft Corporation. All rights reserved. Permission to copy, display and distribute this document is available at: http://msdn.microsoft.com/library/en-us/odcXMLRef/html/odcXMLRefLegalNotice.asp