Revision Summary Date Revision History Revision Class Comments 4/4/2008 0.01 Major Initial Availability 6/27/2008 1.0 Minor Revised and edited technical content 12/12/2008 1.01 Editorial Revised and edited technical content 7/13/2009 1.02 Major Revised and edited the technical content 8/28/2009 1.03 Major Updated and revised the technical content 11/6/2009 1.04 Editorial Revised and edited the technical content 2/19/2010 2.0 Major Updated and revised the technical content 3/31/2010 2.01 Editorial Revised and edited the technical content 4/30/2010 2.02 Editorial Revised and edited the technical content 6/7/2010 2.03 Editorial Revised and edited the technical content 6/29/2010 2.04 Editorial Changed language and formatting in the technical content.
4/11/2012 2.6 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 2.6 None No changes to the meaning, language, or formatting of the technical content. 9/12/2012 2.6 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 2.6.1 Editorial Changed language and formatting in the technical content. 2/11/2013 2.6.1 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 3.0 Major Significantly changed the technical content. 11/18/2013 3.0 None No changes to the meaning, language, or formatting of the
[MS-IPFF] and [MS-IPFF2] section 2.4. BusinessLogic Issues related to declarations as specified in [MS-IPFF] and [MS-IPFF2] section 2.2. Calculations Issues related to calculation declarations, as specified in [MS-IPFF] and [MS-IPFF2] section 2.2. Validation Issues related to declarations. DigitalSignatures Issues related to , as specified in [MS-IPFF] section 2.2.126 and section 2.2.1.2.107. DataAdapters Issues related to , as specified in [MS-IPFF] and [MS-IPFF2] section 2.2. Submit Issues related to . Views Issues related to form views, as specified in [MS-IPFF] and [MS-IPFF2] section 2.2. Rules Issues related to , as specified in [MS-IPFF] and [MS-IPFF2] section 2.2. ConditionalFormatting Issues related to , as specified in [MS-IPFF] and [MS-IPFF2] section 2.4.
183 Controls Could not execute the following relative query [data adapter name]. Relative queries are not allowed for connections linked to the Data Connection Library. As specified in [MS-IPFF] section 2.2.147.33. 184 Controls Cannot run the relative query [query]. Relative queries are not allowed for connections linked to the Data Connection Library. As specified in [MS-IPFF] section 2.2.147.34. 185 Controls relativeQuery/@replace cannot be a relative, local, or UNC path. As specified in [MS-IPFF] section 2.2.147.34. 186 Controls Unsupported HTML constructs were found associated with this Repeating Table. As specified in [MS-IPFF] section 2.4.1.16. 191 Controls A text box is bound to an inappropriate datatype. As specified in [MS-IPFF] section 2.4.1.20. 192 Controls Rule was referenced but not defined: [rulenName]. As specified in [MS-IPFF] section 2.2.132, ruleSet attribute. 193 Controls has been a critical error while processing the form. The protocol server returns this message protocol server when an unknown error was encountered and the protocol server does not have a default method for handling this unknown error. 196 DataAdapters This database is not supported. The database must be a Microsoft SQL Server. The protocol server returns this error message when there is a data adapter that attempts to connection to a database that is not supported by the protocol server . 197 BusinessLogic Unsupported object model version. As specified in [MS-IPFF] section 2.2.147.50, version attribute. 200 GenericXsf The definition of view [view name] does not exist. As specified in [MS-IPFF] sections 2.2.68, 2.2.114, and 2.2.129, transform attribute. 203 GenericXPath A call to GetDOM failed. The DataObject does not exist. As specified in [MS-IPFF] section 2.4.3.9.2. 204 Invalid expression encountered: [XPath expression]. As specified in [XPATH]. 205 Invalid binding XPath [XPath expression]. As specified in [MS-IPFF] section 2.4.1.1, productions LEAF_XPATH, GROUP_XPATH,
11 BrowserCompatibility Controls One or more buttons have the same ID property as this one. The actions associated with the buttons may not execute correctly. As specified in section 2.4.2.10. BrowserCompatibility Controls Unexpected token encountered. Expected an identifier for the class name. The protocol server returns this message when the syntax of a CSS 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 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 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] 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 section 10.2 and section 12.5.1. 54 BrowserCompatibility Controls The form sets the style to a 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 The protocol server will return this message when a form view contains CSS determined to
be modified or removed when the form is shown to the user. be a potential security issue during run time of the 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 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 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-IPFF] section 2.2.147.9. 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-IPFF] section 2.2.147.9.
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-IPFF] section 2.2.115. 110 BrowserCompatibility Controls Printing headers and footers is not supported As specified in [MS-IPFF] section 2.2.115. 153 BrowserCompatibility Controls The useDataSet option is not supported. As specified in [MS-IPFF] section 2.2.39. 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-IPFF] section 2.2.118. 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-IPFF] section 2.2.147.12. 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 The protocol server returns this message when a leaf control has a issue. The detailed message can describe how many preceding related messages are also caused by this issue.
will be displayed as the print view. specified in section 2.2.147.21. 276 BrowserCompatibility Controls Digital signatures are not supported by InfoPath 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 section 2.2.125. Message Elements of Type "Information" ID Category Feature Message Description 37 BrowserCompatibility Controls Unexpected character [character] encountered, expected [character]. The unexpected character will be ignored. The protocol server returns this message when parsing the CSS associated with a form view. The parser expects a "!" character in a comment tag. 38 BrowserCompatibility Controls Unexpected character [character] encountered, expected [character]. The unexpected character will be ignored. The protocol server returns this message when parsing the CSS associated with a form view. The parser expects the "-" character in a comment tag. 39 BrowserCompatibility Controls Unexpected character [character] encountered, expected [character]. The unexpected character will be ignored. The protocol server returns this message when parsing the CSS associated with a form view. The parser expects the second "-" character in a comment tag. 41 BrowserCompatibility Controls Unexpected character encountered. Expected the end of the stylesheet declaration. The protocol server returns this message when parsing the CSS associated with a form view. The parser could not find the end of the style sheet declaration. 43 BrowserCompatibility Controls Unterminated string encountered. This string will be ignored. The protocol server returns this message when parsing the CSS associated with a form view that contains a string where quotes or double quotes are not properly closed. 96 BrowserCompatibility Controls Error in [manifest file name]. Invalid or unsupported value [LCID value] for the lang property of the [xsl file name] file. Ignoring the language attribute for this view. As specified in section 2.2.100.
Messages for InfoPath 2010 Forms Messages described in this section are generated by Microsoft SharePoint Server 2010 and Microsoft SharePoint Server 2013 when design checking a form template (.xsn) file as specified in . Message Elements of Type "Error" ID Category Feature Message Description 1 Controls The form template is not browser-compatible. It might be possible to correct the problem by opening the form template in Microsoft InfoPath, and then republishing it. The protocol server returns this message when the form template file cannot be opened. This error will occur when the file is invalid or corrupt. 5 Controls loading form code assembly: [name of the user code module]. As specified in section 2.2.2.2.43. 6 Controls A rule references a button that is missing from the view. The protocol server returns this error message when a rule is associated with a button control that is not part of the form view. 12 Controls Button [button name] has a value of the xd:action attribute that is not supported in form templates. As specified in [MS-IPFF2] section 2.4.2.1. 13 Controls Expected anchor tag is missing. As specified in [MS-IPFF2] section 2.4.1.12. 14 Controls List Box control is not supported. As specified in [MS-IPFF2] section 2.4.1.13. 16 Controls Combo Box control is not supported. As specified in [MS-IPFF2] section 2.4.1.21. 18 Controls [Control Name] control is not supported. As specified in [MS-IPFF2] section 2.2.1.2.89. 21 Controls Picture control is not supported. As specified in section 2.4.1.23. 22 Controls Ink Picture control is not supported. As specified in [MS-IPFF2] section 2.4.1.22. 23 Controls Horizontal Region control is not supported. As specified in [MS-IPFF2] section 2.4.1.22. 24 Controls Master/detail control is not supported. As specified in [MS-IPFF2] section 2.4.2. 26 Controls Recursive control not supported. As specified in section 2.4.1.23. 28 Controls Scrolling Region control is not supported. As specified in [MS-IPFF2] section 2.4.1.22.
62 Controls An eval expression used in the form has invalid arguments. As specified in [MS-IPFF2] section 2.4.3.6.2. 63 Controls The XPath [xpath expression] is invalid. [error details]. As specified in . 64 Controls The following file is not a valid Xml Schema: [name of the schema file]. As specified in . 67 Controls The following file is either missing or is not part of included in the form template: [filename]. To add a file to the form template in design mode, use the Resource dialog box on the Tools menu, and then add the file. As specified in [MS-IPFF2] section 2.2.1.2.79. 68 Controls Multiple xsl:templates found with name corresponding to this xsl:call-template. Using the first xsl:template found. The protocol server returns this error message when a form view file contains more than one XSL template element with the same value for the name attribute. 69 Controls Did not find an xsl:template with the same name as this xsl:call-template. Ignoring the xsl:call-template. As specified in . 71 Controls Multiple xsl:templates with mode corresponding to this Using the first xsl:template found. The protocol server returns this error message when a form view file contains an apply-templates element that can find one or more xsl:template element to apply with the same mode attribute. 72 Controls The xsl:stylesheet element had multiple xsl:template elements with no mode attribute. This is not supported. Using only the first of these xsl:templates. As specified in [MS-IPFF2] section 2.4.1.2. 73 Controls The mode of this xsl:apply-templates element does not match the mode attribute of any xsl:template element. As specified in [MS-IPFF2] sections 2.4.1.15 and 2.4.1.18. 74 Controls Could not find an xsl:template without a mode inside xsl:stylesheet. As specified in [MS-IPFF2] section 2.4.1.2.
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 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] 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 The protocol server returns this message when the form view contains a control that
settings of the site where the form is activated. 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 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 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 issue. The detailed message can describe how many preceding related messages are also caused by this 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 The protocol server returns this message when a form section has a issue. The detailed message can describe how many preceding related messages are also caused by this issue.
Control Properties dialog box. 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 issue. The server sends this message when a form control has a 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 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 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 to field or group ([XPath expression]) to which other controls are also bound. This can lead to effects that can be evaluated The protocol server returns this message when it detects this form template has a potential issue. This message is returned when a form section has an optimization issue because the
only on the server. .[Optional description and count of any related messages]. 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 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 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 The protocol server returns this message when it detects this form template has a potential issue.
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. 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 views are not supported in forms. Instead a 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 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 section 2.2.1.2.106. 285 BrowserCompatibility Controls The sign signature line rule action is not supported in Web browser 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 contains a SignatureLine element as specified in section 2.2.3.2.12. 286 BrowserCompatibility Controls The code in this form uses methods or properties that require assembly The protocol server returns this message when the form definition (.xsf) file as specified in contains a
[Assembly Name]. reference to an as specified by the following element managedCode as specified in 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 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 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 form template option in the Publishing Wizard. The protocol server returns this message when the view definition (.xsl) file, as specified in contains a Contact Selector as specified in section 2.3.1.3 that has user code.
Index A Abstract data 23 12 22 22 B 46 BrowserEnableUserFormTemplate operation ( 23, 24) C 12 14 19 14 105 Client 23 14 14 14 15 15 18 server 27 18 D Data model - abstract 23 15 DesignCheckFormTemplate operation ( 23, 27) 44 44 45 E Events 43 43 Examples 46 44 44 45 49 51 47 47 48 50 F 20 12 54 G GetListFormLocation operation ( 23, 30) 49 GetUserCodeDeploymentDependencies operation ( 23, 33) 51 7 22 I 53 53 11 Initialization 23 7 L Local events 43 M 15 Message processing 23 Messages 22 22 14 19 14 14 15 13 13 20 22 15 18 21 13 19 18 13 13 18 21 N 13 10 O