Power Apps Form Submit Issue – 7 Common Problems and Fixes

Why Power Apps Form Is Not Submitting? 

Have you ever clicked the Submit button in a Power Apps form and… nothing happened? No error message. No data saved. Just frustration.

This blog solves one very common but confusing problem: Power Apps form submit not working. Whether you are a beginner building your first app or a working professional maintaining an existing solution, this guide will help you understand why forms fail to submit and how to fix them correctly.

• ✔ Understand how Power Apps form submission really works
• ✔ Learn 7 real-world reasons why SubmitForm fails
• ✔ Get copy-ready formulas and practical fixes
• ✔ Avoid common beginner mistakes that waste hours

Introduction: A Real-World Power Apps Problem

Power Apps is designed to make application development easier, especially for people who are not traditional developers. But when something basic like a form submission does not work, it can feel very confusing.

Many developers assume that clicking a button with SubmitForm() will always save data. In reality, Power Apps forms depend on many small configurations. If even one of them is wrong, the form silently fails.

In this article, I am sharing practical experience-based explanations based on real projects using SharePoint, Dataverse, and Microsoft 365.

How Power Apps Form Submission Works (Quick Overview)

• A form is connected to a data source (SharePoint, Dataverse, Excel, etc.)
• The form has a Mode (New, Edit, or View)
• Fields inside the form are data cards bound to columns
• SubmitForm(FormName) sends data to the data source

Reason 1: Form Is in View Mode

Problem

One of the most common issues is that the form is accidentally set to View mode. In View mode, Power Apps does not allow any data changes.

Solution

FormMode.New

Or dynamically control the form mode like this:

If(
    IsBlank(SharePointIntegration.Selected),
    FormMode.New,
    FormMode.Edit
)

Reason 2: SubmitForm Not Connected to the Correct Form

Problem

Many apps have multiple forms. Developers sometimes write SubmitForm(Form1) while the actual form name is different.

Solution

SubmitForm(frmEmployee)

Always select the submit button and verify the form name in the OnSelect property. Rename forms clearly (for example: frmCreateItem, frmEditItem).

Reason 3: Required Fields Are Empty

Problem

SharePoint and Dataverse enforce required columns. If a required field is empty, the form will not submit.

Best Practice Solution

If(
    Form1.Valid,
    SubmitForm(Form1),
    Notify("Please fill all required fields", NotificationType.Error)
)

Look for red asterisks on fields and error messages inside data cards.

Reason 4: Data Type Mismatch

Problem

A very common professional mistake is mapping the wrong control type to a column. For example, saving text into a number column.

Solution

Value(txtAmount.Text)

Always use Value(), DateValue(), or Text() based on column type.

Reason 5: Invalid Patch or Custom Logic

Problem

Mixing Patch() and SubmitForm() incorrectly can block submission.

Solution

SubmitForm(Form1)

If you need full control, use Patch properly:

Patch(
    DataSource,
    Defaults(DataSource),
    {
        Title: txtTitle.Text,
        Amount: Value(txtAmount.Text)
    }
)

Reason 6: Data Source Connection Issues

Problem

If your SharePoint or Dataverse connection is broken or expired, submission may fail without showing an error.

Solution

• Re-authenticate the data source connection
• Check user permissions on the list or table

Reason 7: OnSuccess / OnFailure Logic Blocking UI

Best Practice Solution

Form1.OnSuccess:
Notify("Data saved successfully", NotificationType.Success);
ResetForm(Form1);

Without proper feedback, users may think the form did not submit.

Common Mistakes & Best Practices

• Mistake: Ignoring form validation
  Best Practice: Always use Form.Valid
• Mistake: Hardcoding values
  Best Practice: Use variables and controls
• Mistake: Poor naming conventions
  Best Practice: Use meaningful names

Quick Summary Table

Scenario	Wrong Approach	Correct Approach	Notes
Form mode	View mode	New/Edit mode	DefaultMode matters
Required fields	Ignoring validation	Form.Valid	Mandatory columns
Data type	Wrong mapping	Use Value/Text	SharePoint strict typing

Frequently Asked Questions

Why does SubmitForm not show any error?

Power Apps shows errors inside data cards by default. Always check the form error property.

Should I use Patch or SubmitForm?

Use SubmitForm for simple forms. Use Patch for advanced custom logic.

Does SharePoint calculated column affect submit?

No. Calculated columns run after submit, not during UI interaction.

Conclusion

Power Apps form submission issues are frustrating, but they are usually caused by small configuration mistakes. By checking form mode, required fields, data types, and connections, you can solve most issues quickly.

Apply these fixes step by step and your form will behave correctly. Feel free to share your scenario or questions.

Search Description (120 characters):
Power Apps form not submitting? Learn 7 common reasons, fixes, examples, and best practices for SharePoint and Dataverse

Image Generation Prompts

• Modern Power Apps form UI with submit button and validation errors
• Diagram showing Power Apps form data flow to SharePoint
• Power Apps form modes: New, Edit, View comparison
• Required field validation in Power Apps form
• Patch vs SubmitForm workflow illustration