7.2.2 Message Elements of Type "Warning"

ID

Category

Feature

Message

Description

11

BrowserCompatibility

Controls

One or more buttons have the same ID property as this one. The actions associated with the buttons might not execute correctly.

As specified in [MS-IPFF2] section 2.4.2.10.

32

BrowserCompatibility

Controls

Unexpected token encountered. Expected an identifier for the class name.

The protocol server returns this message when the syntax of a CSS class name that follows a "." flag is invalid.

33

BrowserCompatibility

Controls

Unexpected token encountered. Expected an identifier for an id.

The protocol server returns this message when the syntax of a CSS identifier preceded by a "#" flag is invalid.

34

BrowserCompatibility

Controls

Unexpected token encountered. Expected an identifier for a pseudo style.

The protocol server returns this message when the syntax of a CSS pseudo-style preceeded by a ":" flag is invalid.

35

BrowserCompatibility

Controls

Invalid or malicious CSS styles were found in view [view name].

The protocol server returns this message when the syntax of a CSS associated with a form view contains invalid elements or XML constructs that could permit script injection.

36

BrowserCompatibility

Controls

Unexpected character encountered. It will be ignored.

The protocol server returns this message server when parsing the CSS associated with a form view.

42

BrowserCompatibility

Controls

Potentially unsafe HTML was found in view '[view name]'. It will be modified or removed when the form is shown to the user.

The protocol server will return this message when a form view contains XML determined to be a potential security issue during run time of the browser-enabled form template.

47

BrowserCompatibility

Controls

Unsupported html attribute [attribute name] encountered.

The protocol server returns this message when the form view contains an unsupported XML attribute to describe its layout.

48

BrowserCompatibility

Controls

Unsupported HTML attribute encountered: [attribute name].

The protocol server returns this message when the form view contains an unsupported XML attribute to describe its layout.

50

BrowserCompatibility

Controls

The following HTML tag is not supported: [tag name].

The protocol server returns this message when the form view contains an unsupported XML tag.

51

BrowserCompatibility

Controls

Unsupported value [value] for size attribute on the font element. Defaulting to medium font size (4).

The protocol server returns this message when the form view contains an unsupported value for the font element size attribute.

52

BrowserCompatibility

Controls

The form has a control with border and margin that is too restrictive to properly show error visualization.

The protocol server returns this message when the form view contains a control that cannot properly display the error visualizations UI.

53

BrowserCompatibility

Controls

Unexpected type of list found. Supported values are: '1', 'a', 'A', 'i' and 'I'. Using the default list type.

The protocol server returns this message when it encounters invalid XML list or list item bullet styling, as specified in [HTML] section 10.2 and [CSS-LEVEL2] section 12.5.1.

54

BrowserCompatibility

Controls

The form sets the [css-style-name] style to a value ([css-style-value]) where the unit could not be safely approximated to pixels.

The protocol server returns this message when failing to convert the value of a CSS style value to an appropriate number of pixels.

56

BrowserCompatibility

Controls

Potentially unsafe HTML was found in view [view name]. It will be modified or removed when the form is shown to the user.

The protocol server will return this message when a form view contains CSS determined to be a potential security issue during run time of the browser-enabled form template.

78

BrowserCompatibility

Controls

A default height will be added to a multi-line Text Box control in view [view name] bound to a node [control name].

The protocol server returns this message when encountering a multiline text box control (see [MS-IPFF2] section 2.4.2.11), with a missing height attribute.

84

BrowserCompatibility

Controls

The language pack corresponding to the form locale [locale name] that has not been installed on the server. Text generated by InfoPath Forms Services, such as menus, messages, and dialog boxes, will use the locale and language settings of the site where the form is activated.

As specified in [MS-IPFF2] section 2.2.2.2.2.

85

BrowserCompatibility

Controls

The language pack corresponding to the form locale [LCID] that has not been installed on the server. Text generated by InfoPath Forms Services, such as menus, messages, and dialog boxes, will use the locale and language settings of the site where the form is activated.

As specified in [MS-IPFF2] section 2.2.2.2.2.

109

BrowserCompatibility

Controls

Printing headers and footers is not supported in server forms. The form printed from the browser will not have a header or footer.

As specified in [MS-IPFF2] section 2.2.1.2.96.

110

BrowserCompatibility

Controls

Printing headers and footers is not supported.

As specified in [MS-IPFF2] section 2.2.1.2.96.

153

BrowserCompatibility

Controls

The useDataSet option is not supported.

As specified in [MS-IPFF2] section 2.2.1.2.20.

187

BrowserCompatibility

Controls

Unsupported border styles were found associated with this Repeating Table. They have been converted to solid border. The conversion to solid border is for Internet Explorer® only.

The protocol server returns this error message when a Repeating Table Control uses the border-style attribute and is setting its value to a string different from "solid", "none", or "hidden".

199

BrowserCompatibility

Views

The view attribute xsf:toolbar is not supported.

As specified in [MS-IPFF2] section 2.2.1.2.99.

222

BrowserCompatibility

GenericXsf

A toolbar button element in the form definition file (manifest.xsf) has the following error: [XML of the xsf2:command element].

As specified in [MS-IPFF2] section 2.2.2.2.5.

243

BrowserOptimization

Controls

By default this control will send data to the server whenever its value changes. Reason: [details]. This can lead to effects that can be evaluated only on the server. [Optional description and count of any related message] To override this behavior, modify Postback Settings on the Browser Forms tab of the Control Properties dialog box.

The protocol server returns this message when a leaf control has a browser-optimization issue. The detailed message can describe how many preceding related messages are also caused by this browser-optimization issue.

244

BrowserOptimization

Controls

By default this control will send data to the server on insert or delete. Reason: [details]. This can lead to effects that can be evaluated only on the server. [Optional description and count of any related messages] To override this behavior, modify Postback Settings on the Browser Forms tab of the Control Properties dialog box.

The protocol server returns this message when a form section has a browser-optimization issue. The detailed message can describe how many preceding related messages are also caused by this browser-optimization issue.

245

BrowserOptimization

Controls

By default this control will send data to the server on insert or delete. Reason: Other related controls require evaluation on the server. For more information, see the following 'primary cause' message in the Design Checker. To override this behavior, modify Postback Settings on the Browser Forms tab of the Control Properties dialog box.

The protocol server returns this message when it detects this form template has a potential browser-optimization issue. The server sends this message when a form control has a browser-optimization issue that is caused by another control in the same form view. A related message will appear later in the message list that identifies the other control that causes the browser-optimization issue with this control.

257

BrowserOptimization

Controls

Other controls are bound to the same field or group ([XPath expression]). This can lead to effects that can be evaluated only on the server. [Optional description and count of any related message]

The protocol server returns this message when it detects this form template has a potential browser-optimization issue. This message is returned when the optimization issue is because multiple controls have the same binding.

258

BrowserOptimization

Controls

This section contains a control bound to field or group ([XPath expression]) to which other controls are also bound. This can lead to effects that can be evaluated only on the server. .[Optional description and count of any related messages].

The protocol server returns this message when it detects this form template has a potential browser-optimization issue. This message is returned when a form section has an optimization issue because the binding of a control is inside the form section.

259

BrowserOptimization

Controls

The section is bound to the root node ([XPath expression]) of the data source. This can lead to effects that can only be evaluated on the server.[Optional description and count of any related message].

The protocol server returns this message when it detects this form template has a potential browser-optimization issue. The server returns this message when a form section is binding to the root element.

262

BrowserCompatibility

Controls

Conditionally formatting a File Attachment control is not supported in server forms.

As specified in [MS-IPFF2] section 2.4.1.11.

263

BrowserOptimization

Controls

The binding of this section ([binding]) can lead to effects that can be evaluated only on the server. Reason: [postback reason].As a result, other section or table controls must also send data to the server on insert or delete. For more information, see the preceding [count] message or messages in the Design Checker.

The protocol server returns this message when it detects this form template has a potential browser-optimization issue. This particular message is returned when a Section Control is determined to be a likely cause of the issue.

264

BrowserOptimization

Controls

By default this button will send data to the server whenever it is clicked. Reason: It is associated with a rule that uses the following expression that can be evaluated only on the server: [postback reason].To override this behavior, modify Postback Settings on the Browser Forms table of the Button Properties dialog box.

The protocol server returns this message when it detects this form template has a potential browser-optimization issue. This particular message is returned when a XPath expression used by a Button Control is a likely cause of the issue.

275

BrowserCompatibility

Controls

Merged print views are not supported in browser-enabled forms. Instead a read-only view of the current view will be displayed as the print view.

The protocol server returns this message when the form definition (.xsf) file contains an mergedPrintView element as specified in [MS-IPFF2] section 2.2.1.2.14.

276

BrowserCompatibility

Controls

Digital Signatures are not supported by InfoPath Forms Services for list forms. All digital signatures must be removed before the form can be published.

The protocol server returns this message when the form definition (.xsf) file contains an signedDataBlock element as specified in [MS-IPFF2] section 2.2.1.2.106.

285

BrowserCompatibility

Controls

The sign signature line rule action is not supported in Web browser forms. The rule will be ignored when the form is edited in a Web browser.

The protocol server returns this message when the form definition (.xsf) file as specified in [MS-IPFF2] contains a SignatureLine element as specified in [MS-IPFF2] section 2.2.3.2.12.

286

BrowserCompatibility

Controls

The code in this form uses methods or properties that require assembly [Assembly Name].

The protocol server returns this message when the form definition (.xsf) file as specified in [MS-IPFF2] contains a reference to an assembly as specified by the following element managedCode as specified in [MS-IPFF2] section 2.2.2.2.43 that cannot be found when the form is being published.

298

BrowserCompatibility

Controls

Never postback setting is not supported for the Button control in this version of InfoPath. In the Browser forms tab of the Button control properties dialog box, change the postback setting to the recommended option.

The protocol server returns this message when the form definition (.xsf) file contains a button control, as specified in [MS-IPFF2] section 2.4.1.5, that has the postback setting, as specified in [MS-IPFF2] section 2.4.2.29 set to "Never".

303

BrowserCompatibility

Controls

Unsupported text indentation formatting (first line or hanging) was found in view [View Name]. Use clear formatting to remove first line or hanging text indentation.

The protocol server returns this message when the view definition (.xsl) file, as specified in [MS-IPFF2], contains a text indentation style markup.

304

BrowserCompatibility

Controls

Code events on Person/Group Picker controls are not supported in sandboxed solutions. To enable code events on Person/Group Picker controls use the administrator-approved form template option in the Publishing Wizard.

The protocol server returns this message when the view definition (.xsl) file, as specified in [MS-IPFF2], contains a Contact Selector as specified in [MS-IPFF2] section 2.3.1.3 that has user code.