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 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 from real projects using SharePoint, Dataverse, and Microsoft 365.

How Power Apps Form Submission Works (Quick Overview)

• A form is connected to a data source
• The form has a Mode (New, Edit, View)
• Data cards are bound to columns
• SubmitForm(FormName) sends data to the source

Reason 1: Form Is in View Mode

Problem

One common issue is the form being accidentally set to View mode. In View mode, Power Apps does not allow data changes.

Solution

FormMode.New

Or dynamically:

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

Reason 2: SubmitForm Not Connected to the Correct Form

Problem

Many apps have multiple forms and developers sometimes use the wrong form name.

Solution

SubmitForm(frmEmployee)

Always verify the form name inside OnSelect.

Reason 3: Required Fields Are Empty

Best Practice Solution

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

Reason 4: Data Type Mismatch

Solution

Value(txtAmount.Text)

Reason 5: Invalid Patch or Custom Logic

Solution

SubmitForm(Form1)

If using Patch:

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

Reason 6: Data Source Connection Issues

• Re-authenticate the data source
• Check user permissions

Reason 7: OnSuccess / OnFailure Logic Blocking UI

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

Common Mistakes & Best Practices

• Mistake: Ignoring validation — Use: Form.Valid
• Mistake: Hardcoding values — Use: variables
• Mistake: Poor naming — Use: meaningful names

Quick Summary Table

Scenario	Wrong Approach	Correct Approach	Notes
Form mode	View mode	New/Edit mode	Mode matters
Required fields	Ignored	Use Form.Valid	Mandatory columns
Data type	Wrong mapping	Use Value/Text	Strict typing

Frequently Asked Questions

Why does SubmitForm not show any error?

Errors appear inside data cards. Check error properties.

Patch or SubmitForm?

SubmitForm = simple forms, Patch = advanced logic.

Do calculated columns affect submit?

No. They run after submission.