Troubleshoot an InfoPath Form Submission Warning on a SharePoint Communication Site
Question details
The user needs to determine why an InfoPath form submits successfully on one SharePoint communication site but displays a warning on another.

- Product
- Microsoft InfoPath and SharePoint
- Device & OS
- not provided
- Scenario
- Submitting an InfoPath form on two SharePoint communication sites and comparing the results.
- Observed behavior
- Submission succeeds on one site, while another site displays a warning. The complete warning text and whether the second submission saves successfully are not provided.
Capture the full warning text and identify the destination list or form library on each site. Arrange access to both sites' settings and the InfoPath form configuration so you can compare them under equivalent user permissions.
Compare the SharePoint destinations and InfoPath submission settings
Use the working site as a reference to identify differences in permissions, destination structure, and form configuration.
A warning on only one site does not establish whether the cause is the form or the site. Compare the actual submission destinations rather than assuming that the communication site type is responsible.
Submit the form on each site using equivalent test values and user access. Copy the complete warning text, then open the destination list or form library to check whether the affected submission was saved.
Open the destination list or library on each site, select Settings > List settings or Library settings, and open Permissions for this list or Permissions for this document library. Compare permission inheritance and the submitting user's effective access.
In List settings or Library settings, compare column names, types, required-field settings, and validation rules. Compare content types if they are enabled, including any required fields that differ between the destinations.
Check Workflow Settings where available and review any automation associated with each destination. For a customized list form, compare Form settings; for a form library, check Advanced settings and the configured document template.
Open the form template in InfoPath Designer. Review Data > Data Connections and Data > Submit Options, then inspect any rules attached to the Submit button. Confirm that destination URLs, field references, and connection settings match the intended site.

Isolate the field or rule that triggers the warning
Use controlled tests when comparing the two destinations does not reveal the cause.
Use WPS Office to Document Your SharePoint Troubleshooting
WPS Office is a free, lightweight alternative for everyday documents and spreadsheets, with a familiar interface and Microsoft Office format compatibility that helps ease migration. Use Writer or Spreadsheets to record warning messages, compare site settings, and share test results. WPS Office does not repair InfoPath forms or configure SharePoint submissions.

Frequently Asked Questions
Does the warning mean that the form was not submitted?
Not necessarily. After the warning appears, open the destination SharePoint list or form library and check for the submitted item or document. The exact warning text and saved result are needed to distinguish a failed submission from a warning that occurs after saving.
Why can the same InfoPath form work on one site but warn on another?
The destinations may differ in permissions, required columns, validation rules, content types, workflows, or form settings. The form may also use a different submit connection or destination URL. Compare List settings or Library settings on both sites and review Data > Data Connections in InfoPath Designer.
What should I check first if only certain users receive the warning?
Open the destination's List settings or Library settings and review its permissions, including whether it inherits access from the site. Compare affected and unaffected users' effective access, then test with equivalent form values. Avoid granting broad permissions without identifying the required access.
How can I find out whether one field causes the warning?
Use a test copy in InfoPath Designer and isolate one field or associated rule at a time. Repeat the same submission after each change, then restore the suspected field to confirm whether the warning returns. Check dependencies before removing fields.
Can WPS Office fix the InfoPath submission warning?
No. This issue requires investigation in InfoPath and SharePoint. WPS Writer and Spreadsheets can help document the warning, compare site configurations, and share troubleshooting notes in .docx or .xlsx format.




