InfoPath 2013

  1. The form template was imported successfully, but one or more potential issues were identified. To review these issues, see ...
  2. The form that you selected is not available and may have been removed by another user. To fix this problem, try opening a ...
  3. The form was not submitted because a form named %1!s! already exists in the document library at %2!s!. Please contact the ...
  4. The form you are attempting to open may be located on a different server. This form can only be opened using Microsoft InfoPath. ...
  5. The form you are opening requires a new version of the form template. To upgrade the form template, close all the forms based ...
  6. The formatting options selected for this rich text box control are not supported in %1!s!.To fix this problem, change the ...
  7. The function 'userName' is not supported in (!idspnInfoPath_Short_2003).The function occurs in a %1!s!.All uses of the function ...
  8. The function 'userName' is not supported in (!idspnInfoPath_Short_2003).The function occurs in the data connection named ...
  9. The function used to retrieve the current user's role (xdXDocument:get-Role) is not supported in %2.This function is currently ...
  10. The functions position() and last() are not supported in %2.To fix this problem, modify or remove any XPath expressions that ...
  11. The functions position() and last() are not supported in %2.To fix this problem, modify or remove the following data connection: ...
  12. The header for this form has been customized in the form definition (.xsf) file. If you modify the header in InfoPath, this ...
  13. The InfoPath form template for the selected content type cannot be loaded. The form template was not designed for InfoPath ...
  14. The language pack corresponding to the form locale "{0}" you have chosen has not been installed on the server. Text generated ...
  15. The lookup field is not valid because the reference list or list column does not exist. Delete the field and recreate it. ...
  16. The merge action cannot be changed because no additional merge actions are available for the data type of this field.To merge ...
  17. The merge actions for this form template cannot be loaded or modified. The merge XSL transform may have been customized and ...
  18. The merge cannot be started, because the form template is not available on your computer.To fix this problem, make sure that ...
  19. The merge cannot be started, because the merge feature is disabled for the selected form template. To fix this problem, contact ...
  20. The merge cannot be started. An incorrect version of InfoPath is installed. Install correct version of InfoPath and verify ...
  21. The merge cannot be started. Verify that InfoPath is installed correctly and that any programs that may interfere with InfoPath ...
  22. The merge settings for attributes of repeating fields cannot be customized. Attributes of repeating fields automatically ...
  23. The merge settings of the parent group prevent this field from being merged directly with other fields of this type. To change ...
  24. The merge settings of the parent group prevent this group from being merged directly with other groups of this type. To change ...
  25. The multi-select list box control is not supported in (!idspnInfoPath_Short_2003).When the form is filled out in (!idspnInfoPath_Short_2003), ...
  26. The multiple-selection list box control is not supported in %1.When the form is filled out in (!idspnInfoPath_Short_2003), ...
  27. The name of the following file, which is part of the form template, contains non-ASCII characters, the number sign (#), or ...
  28. The number of columns in the master table must be between 1 and 63. The number of fields in the detail section must be between ...
  29. The OpenIn query parameter, if present, must have one of the allowed values: 'Browser', 'Client', 'PreferClient' or 'Mobile'. ...
  30. The operation for the Web service requires values for the parameters listed below. The current values match the sample values ...
  31. The operation requested in the Soap message with soapAction %1 isn't defined in the WSDL file. This may be because it is ...
  32. The operation that you selected uses a DataSet object. InfoPath will track changes to the data and can include that information ...
  33. The option to include data only for the active form in a (!idspnSharePoint) library or list is not supported in (!idspnInfoPath_Short_2003).Before ...
  34. The original form template for this form cannot be found.Another form template, "%1!s!", can be used to open the form. Do ...
  35. The parameterOrder attribute for operation %1 was invalid. It either did specify the same parts multiple times or not all ...
  36. The project location for C# and Visual Basic .NET cannot be changed because Visual Studio Tools for Applications was used ...
  37. The publish operation could not be completed. It cannot be determined if the form template was successfully published. Try ...
  38. The publish operation could not be completed. It cannot be determined if the form template was successfully published. Try ...
  39. The reference to one of the views in the form definition (.xsf) file contains only spaces. This reference cannot contain ...
  40. The Refresh button can refresh either one or all of the secondary data sources, using the corresponding data connections. ...
  41. The requested WSDL does not contain a service section indicating the address of the Web service. If the Web service is registered ...
  42. The rich text field contains nested formatting which is not supported on InfoPath Forms Services. The formatting may be heavily ...
  43. The root element of the form definition (.xsf) file does not belong to the following namespace: http://schemas.microsoft ...
  44. The schema cannot be used because (!idspnInfoPath) does not support elements with an ENTITIES data type. To use this schema ...
  45. The schema cannot be used because (!idspnInfoPath) does not support elements with an ENTITY data type.To use this schema ...
  46. The schema defines an abstract type as an inline complex type in element %1!s!. (!idspnInfoPath) does not support this construct. ...
  47. The schema for the form template cannot be found. (!idspnExcel_NV) will create a schema based on the XML data in the form. ...
  48. The schema for the form template cannot be found. Microsoft Excel will create a schema based on the XML data in the form. ...
  49. The script running in this form is causing (!XDOCS_APP_SHORT_NAME_PLACEHOLDER) to run slowly. If the script continues to ...
  50. The section is bound to the root node ({0}) of the data source. This can lead to effects that can only be evaluated on the ...
  51. The selected control cannot be inserted within itself. A recursive section must be bound to a reference group that contains ...
  52. The selected control cannot display data correctly because its data formatting does not match the data type of the field. ...
  53. The selected control cannot repeat here because the field to which it is bound is not part of the correct group. The field ...
  54. The selected control cannot store data because it is bound to a field or group that will not be included by default when ...
  55. The selected control cannot store data because it is bound to a field with a data type that does not match the control. You ...
  56. The selected control cannot store data because it is bound to a field with a data type that does not match the control. You ...
  57. The selected control cannot store data because it is not bound to a field or group in the data source.To bind the control ...
  58. The selected control cannot store data correctly because it is not in the correct repeating choice group. You can do one ...
  59. The selected control cannot store data correctly, because it is not in the correct repeating section or repeating table. ...
  60. The selected control cannot store data, because it is bound to a non-repeating field or group, but the control itself repeats. ...
  61. The selected control cannot store data, because it is bound to a repeating field or group, but the control itself does not ...
  62. The selected control is bound to the same field or group as another control, which means the two controls will store the ...
  63. The selected control will not work correctly because it is part of a recursive section and is bound to a field that is not ...
  64. The selected data file does not match the current form template. You can select a different data file, or you can preview ...
  65. The selected database connection saves passwords in a plain text file. Because plain text files are unencrypted and because ...
  66. The selected document library does not contain an InfoPath form template. Create a new InfoPath document library if you want ...
  67. The selected field or group contains characters in the XPATH definition that cannot be displayed in form library columns. ...
  68. The selected field or group contains characters in the XPATH definition that cannot be displayed in Web Part connection parameters. ...
  69. The selected form cannot be opened correctly because it was signed with a certificate that is either expired, revoked, not ...
  70. The selected form template cannot be overwritten with the active form template. To publish the active template, publish it ...
  71. The selected library does not contain an InfoPath form template. Click Publish New to create a new form library, or select ...
  72. The selected Office data connection (.odc) file is missing required information. The following property is missing or invalid: ...
  73. The selected XML document cannot be used as a data connection source because it has not been added to the form template as ...
  74. The selected XML Schema contains more than one occurrence of the following field or group: %1!s! in the same context. (!idspnInfoPath) ...
  75. The selected XML Schema contains more than one root. InfoPath can only create a form template based on one of the roots.&Select ...