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

Validate the generated app before publishing

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

Quick answer

In short

Do not publish only because the package imports. Validate every generated screen, data source, dropdown, checkbox, required field, save action, and important rule with real test records.

Most likely cause

Most remaining problems are not import failures; they are mismatches between InfoPath behavior and the generated Power Apps scaffold.

What to do next

Use a small smoke-test script first, then run business-owner UAT on the highest-risk sections.

Smoke test script

  1. Open the app in Preview.
  2. Visit every generated screen or virtual screen.
  3. Open every dropdown and confirm it returns expected rows.
  4. Toggle every checkbox and confirm visual state changes.
  5. Enter required and optional field values.
  6. Submit a test item.
  7. Open SharePoint and confirm saved columns.
  8. Reopen the app item and confirm values load back into controls.

High-risk areas

  • Secondary-list dropdowns and filtered role lists.
  • Set-value and submit rules.
  • Show/hide sections and virtual-screen navigation.
  • People/person fields and email values.
  • Repeating sections and attachments.

When to publish

Publish after the smoke test passes, the business owner has validated important paths, and any manual rebuild items have an owner or documented workaround.

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

Export7 min read

Import the generated .msapp into Power Apps Studio

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

Export6 min read

Reconnect SharePoint data sources after import

Fix SharePoint connection prompts and confirm the app points at the destination site, list, libraries, and supporting lookup lists.

Export8 min read

Common .msapp import and Studio errors

Resolve common package import, data source, formula, and control errors after opening the generated app.