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

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.

Quick answer

In short

For multi-view forms, each InfoPath view should become a Power Apps screen named from the original InfoPath view.

Most likely cause

If only the default view is generated, the converter likely missed view-specific controls from the XSL view files.

What to do next

Check the Views tab before export and then confirm Power Apps Studio shows one screen per detected view.

Expected output

  • One generated screen per InfoPath view.
  • Screen names based on the InfoPath view names.
  • The default InfoPath view used as the generated app start screen.
  • Controls matched per view, not only from the default view.

Views with no fields

A view may intentionally contain only confirmation text, images, or buttons. When a view should have fields but imports empty, inspect the XSL view file and field mappings because the controls may have been hidden, read-only, or bound to a secondary data source.

Post-import review

  1. Open Tree view in Power Apps Studio.
  2. Confirm all expected screen names are present.
  3. Open each screen and check whether the right fields, images, and buttons are present.
  4. Test navigation buttons between screens.

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

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.

Rules6 min read

Switch-view rules and navigation buttons

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

Views6 min read

Choose layout columns and review field order

Use generated layout settings to make the app easier to scan without reproducing every InfoPath table cell.