Common screen patterns
One view → one screen
Simple forms can stay as a single generated screen with a standard EditForm.
Many views → many screens
Each InfoPath view can become a Power Apps screen named from the original view.
Show/hide → virtual screens
Single-view forms that use ShowHide fields can be split into task-focused screens.
Button behavior
- Navigation buttons can map to Navigate(...) when the target view or virtual screen is clear.
- Submit and save buttons can scaffold SubmitForm(...) or save patterns for builder review.
- Image buttons can be carried over as image assets or converted to standard buttons depending on settings.
- Complex button rule chains should remain flagged for builder review.
Layout guidance
Imported images and buttons should support the task, not push form content off screen. Use the Required Settings options to disable original buttons or images when they create clutter instead of clarity.
Common questions
Can every InfoPath view become a screen?
Yes for screen structure, but views with no editable controls may generate placeholders or visual-only screens until the source controls are mapped.
Can I turn off imported buttons or images?
Yes. Required Settings includes options to skip buttons and/or images from the original form.
Should the generated app copy the exact InfoPath layout?
Not always. The goal is a usable Power Apps replacement. Pixel-perfect InfoPath layouts often need simplification.