2.2.4.4 Message

  • Article

Namespace: http://schemas.microsoft.com/office/infopath/2007/formsServices

The Message element indicates a specific issue the protocol server found within a form template during the browser-enable or design check processes.

 <xs:complexType name="Message" xmlns:xs="http://www.w3.org/2001/XMLSchema">
   <xs:sequence>
     <xs:element minOccurs="0" maxOccurs="1" name="ShortMessage" type="xs:string"/>
     <xs:element minOccurs="0" maxOccurs="1" name="DetailedMessage" type="xs:string"/>
     <xs:element minOccurs="0" maxOccurs="1" name="SourceLocation" type="tns:SourceLocation"/>
   </xs:sequence>
   <xs:attribute name="Id" type="xs:int" use="required"/>
   <xs:attribute name="Type" type="tns:MessageType" use="required"/>
   <xs:attribute name="Feature" type="tns:Feature" use="required"/>
   <xs:attribute name="Category" type="tns:Category" use="required"/>
 </xs:complexType>

ShortMessage:  A Unicode string suitable for display in the protocol client describing the issue. This element MUST have a value populated by the protocol server.

DetailedMessage:  A Unicode string suitable for display in the protocol client describing the issue.

Any localized Unicode strings returned by the protocol server SHOULD be in the language requested by the protocol client in the associated Web service call. If the protocol server is unable to provide strings in the requested language, the protocol server MAY<3> use any available language.

SourceLocation:  Specified in section 2.2.4.6.

Id:  Specifies an integer that identifies the type of Message element.

Type:  Specified in section 2.2.5.3.

Feature:  Specified in section 2.2.5.2.

Category:  Specified in section 2.2.5.1.

The following table specifies a set of reserved Message elements. For the check specified in the Description column, a protocol server MUST construct a Message element matching the details in the table row, in conjunction with the table specified in section 2.2.4.6. A protocol server MUST NOT redefine the Id attribute for any Message element in the following table<4>.

For the reserved elements in the following table, ShortMessage and DetailedMessage are overwritten by the protocol client.

Either the InfoPath Form Template Format Structure, as specified in [MS-IPFF], or the InfoPath Form Template Format Version 2 Structure, as specified in [MS-IPFF2], MUST be used as described in section 1.7.

Id

Category

Feature

Type

Description

44

Browser-Compatibility

Controls

Error

This message MUST be generated when the form definition (.xsf) file contains an invalid documentSignatures element, as specified in [MS-IPFF] section 2.2.125 and [MS-IPFF2] section 2.2.1.2.106.

65

Browser-Compatibility

Controls

Error

This message MUST be generated when the form definition (.xsf) file contains an invalid xmlToEdit element, as specified in [MS-IPFF] section 2.2.124 and [MS-IPFF2] section 2.2.1.2.105.

70

Browser-Compatibility

Controls

Error

This message MUST be generated when the form view file contains an invalid construct, as specified in [MS-IPFF] section 2.4.1.23 and [MS-IPFF2] section 2.4.1.24.

104

Browser-Compatibility

Controls

Error

This message MUST be generated when the form definition (.xsf) file contains an unsupported roles element, as specified in [MS-IPFF] section 2.2.81 and [MS-IPFF2] section 2.2.1.2.62.

105

Browser-Compatibility

Controls

Error

This message MUST be generated when the form definition (.xsf) file contains an unsupported save element as specified in [MS-IPFF] section 2.2.80 and [MS-IPFF2] section 2.2.1.2.61.

106

Browser-Compatibility

Controls

Error

This message MUST be generated when the form definition (.xsf) file contains an unsupported scripts element as specified in [MS-IPFF] section 2.2.33 and [MS-IPFF2] section 2.2.1.2.14.

108

Browser-Compatibility

Controls

Error

This message MUST be generated when the form definition (.xsf) file contains an unsupported importParameters element that contains a useScriptHandler attribute set to "yes" as specified in [MS-IPFF] section 2.2.67 and [MS-IPFF2] section 2.2.1.2.58.

146

Browser-Compatibility

Controls

Warning

This message MUST be generated when the form definition (.xsf) file contains an errorMessage element as specified in [MS-IPFF] section 2.2.64 and [MS-IPFF2] section 2.2.1.2.45 and the value of the type attribute is not "modeless".

154

Browser-Compatibility

Controls

Error

This message MUST be generated by the protocol server when the form definition (.xsf) file contains an adoAdapter element, as specified in [MS-IPFF] section 2.2.38 and [MS-IPFF2] section 2.2.1.2.19, that is configured to submit the form file.

188

Browser-Compatibility

Controls

Error

This message MUST be generated when the form template (.xsn) file contains a dialogBoxExpressionAction element as specified in [MS-IPFF] section 2.2.137 and [MS-IPFF2] section 2.2.1.2.118.

190

Browser-Compatibility

Controls

Warning

This message MUST be generated when the form definition (.xsf) file contains a closeDocumentAction element with attribute promptToSaveChanges that has the value "yes" as specified in [MS-IPFF] section 2.2.142 and [MS-IPFF2] section 2.2.1.2.124.

282

Browser-Compatibility

Controls

Error

This message MUST be generated when the form definition (.xsf) file contains a dataObject element, as specified in [MS-IPFF2] section 2.2.1.2.17, that references a bdcAdapter element, as specified in [MS-IPFF2] section 2.2.1.2.129, along with additional references in the dataObject elements.

283

Browser-Compatibility

Controls

Error

This message MUST be generated when the form definition (.xsf) file contains a Signature Line Control, as specified in [MS-IPFF2] section 2.2.3.2.12.

284

Browser-Compatibility

Controls

Error

This message MUST be generated when a form definition (.xsf) file contains a List Control element, [MS-IPFF2] section 2.4.1.21.7, with the attribute xctname that has the value "ListItem_Formatted".

294

Browser-Compatibility

DataAdapters

Error

This message MUST be generated when a form definition (.xsf) file contains a dataObject element, as specified in [MS-IPFF2] section 2.2.1.2.17, that references a UNC path or local path.