How the pattern works in InfoPath
Many InfoPath applications use one view named Home and fields such as ShowHideHome, ShowHideStudentsList, or ShowHideEditStudent. Buttons set one field to Show and the others to Hide. InfoPath then conditionally displays the matching section.
Power Apps pattern
- Promote each major show/hide section to a screen.
- Generate navigation buttons from the original show/hide rules.
- Avoid duplicating every hidden section on the Home screen.
- Keep shared header or navigation assets only where useful.
Validation focus
Virtual screens are a strong scaffold, but they need validation because the original form may have relied on hidden fields, repeated sections, secondary lists, and read-only detail areas that require a deliberate Power Apps data pattern.