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

Choose layout columns and review field order

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

Quick answer

In short

Form Migrator uses the InfoPath view order when it can, then falls back to SharePoint/schema order. Choose a column count that fits the form and test on the intended screen size.

Most likely cause

Old InfoPath layouts often used dense tables that do not translate cleanly to a responsive Power Apps canvas.

What to do next

Use two columns for most desktop forms, one column for long or narrow forms, and more columns only for compact review screens.

Recommended defaults

  • Two columns for standard desktop data-entry forms.
  • One column for long forms, narrow screens, or mobile-oriented layouts.
  • Three or four columns only for compact admin/review screens where labels and values are short.

Why exact layout is hard

InfoPath XSL views often use tables, merged cells, hidden regions, and inline styling. Power Apps uses screens, containers, forms, and cards. The goal is a clean migration scaffold, not a fragile pixel-perfect HTML conversion.

Post-import cleanup

  1. Open each screen in Power Apps Studio.
  2. Check whether important fields are visible without excessive scrolling.
  3. Move high-priority fields toward the top.
  4. Group related fields visually.
  5. Remove duplicate labels or decorative carryover that does not help users complete the task.

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.

Views7 min read

Carry over original buttons and images

Decide when to include InfoPath buttons, picture buttons, logos, and large images in the generated app.

Export8 min read

Validate the generated app before publishing

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