Sign up / Sign in
Supported6 min readUpdated June 5, 2026

Switch-view rules and navigation buttons

Translate InfoPath view switching into Power Apps Navigate formulas and screen buttons.

Quick answer

In short

Simple InfoPath Switch View actions should become Power Apps Navigate formulas targeting the generated screen with the same view name.

Most likely cause

Navigation fails when the target InfoPath view did not become a screen or when a button rule was not associated with the visual button.

What to do next

Confirm each target screen exists, then test every generated button in Preview mode.

Expected formula pattern

A straightforward view switch becomes a formula such as Navigate('Section 2', ScreenTransition.None). The exact screen name should match the generated Power Apps screen name.

What to validate

  • Buttons appear on the expected screen.
  • OnSelect points at the intended generated screen.
  • The destination screen loads with the expected fields and assets.
  • The user can return to the previous step or home screen.

When manual cleanup is needed

If a button also sets values, submits data, validates fields, or calls script before switching views, the generated Navigate formula is only part of the behavior. Review the full rule details and add the missing Power Fx or Power Automate logic.

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

Views6 min read

Multiple InfoPath views become Power Apps screens

Confirm each InfoPath view is represented as a screen and that the screen name matches the original view name.

Views8 min read

Single-view show/hide forms and virtual screens

Handle InfoPath forms that have one view but use rules to show and hide many sections.

Rules7 min read

Submit and save rules

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