All Accusoft forms-processing components rely on this object to hold their parameters and private data. In general, the Content property holds the parameters or private data and the Type property indicates which component uses the content and also how it uses the content.

FormSetFile or FormDefinitionFile objects write DataItem objects to a form set or form definition file. Normally, the Content property will contain a valid XML fragment, however it may contain any string, including invalid XML fragment. Special characters such as "<" and "&" can also be contained. These characters will not corrupt the form set or form definition file.

Ideally, Content should contain a valid XML fragment and all the elements should be in a unique namespace. Using a unique namespace will insure that a future version of this component will never cause a conflict with your element names.

The XML fragment below is a hypothetical set of scanner settings. The intent is to show a properly-formatted content string, not to show the best way to configure a scanner. Note that the Parameters element has a private namespace of "http://www.mycompany.com/myproduct". The XML specification requires that an XML parser also apply that namespace to all child elements, so there is no need to duplicate it for the Resolution and Brightness elements. Attributes do not need to be placed into a namespace.

Type = "_Scanner" Content = <Parameters xmlns="http://www.mycompany.com/myproduct"> <Resolution x="300" y="300" /> <Brightness mode="Auto" /> </Parameters>

Accusoft components will never use content whose type begins with an underscore, "_". If you create your own content, your type should always begin with an underscore. This will insure that a future Accusoft components will never cause a conflict with your DataItem.

System.Object
   Accusoft.FormDirectorSdk.DataItem

Reference

DataItem Members
Accusoft.FormDirectorSdk Namespace