Sign up / Sign in
Builder review7 min readUpdated June 5, 2026

Submit and save rules

Map InfoPath submit behavior to standard SharePoint form submit, Patch, or Power Automate follow-up work.

Quick answer

In short

Standard SharePoint save behavior can be generated, but InfoPath submit rules may include additional actions that must be validated or rebuilt.

Most likely cause

InfoPath Submit may have saved XML to a library, sent email, set status fields, switched views, or closed the form. A single SubmitForm formula may not cover all of that.

What to do next

Identify what the submit rule did, validate the generated save, then add any extra notifications, status updates, or workflow calls.

Common submit patterns

  • Save to the primary SharePoint list.
  • Submit XML to a form library.
  • Set status or approval fields before submit.
  • Send email or call a data connection.
  • Switch to a confirmation view after submit.

Generated first pass

For a SharePoint-backed list form, the generated app usually uses standard form submit behavior. That covers primary field saves but does not automatically prove every side effect from the InfoPath submit button was reproduced.

Validation checklist

  1. Submit a new record.
  2. Confirm every mapped column saves correctly.
  3. Confirm required fields block or allow save as expected.
  4. Confirm status/default fields are set.
  5. Confirm any expected post-submit navigation or notification behavior.

Keep reading the next most relevant guides for this form pattern.

Export8 min read

Validate the generated app before publishing

Run a focused test pass that covers screens, dropdowns, labels, checkboxes, save behavior, and business rules.

Rules8 min read

Set-value, default, and calculation rules

Know what can be scaffolded as Power Fx and what needs formula cleanup after import.

Export7 min read

Import the generated .msapp into Power Apps Studio

Open the package in Power Apps Studio and start the maker validation pass.