Supported7 min readUpdated June 5, 2026

How to read the Analyze screen

Use the summary, tabs, warnings, and detected connections to decide whether the form is ready for mapping.

Quick answer

In short

Analyze is the triage screen. It tells you what was detected, what needs review, and where the next setup step should focus.

Most likely cause

Users often mistake Analyze for the final conversion result. It is the compatibility and discovery report, not the finished app.

What to do next

Check Warnings first, then Views, Connections, and Rules. Continue only when the detected form structure matches the source form.

What each tab is for

  • Summary: first-pass readiness and the most important counts.
  • Views: InfoPath views or virtual sections that may become Power Apps screens.
  • Rules: navigation, set-value, submit, show/hide, and manual-review logic.
  • Connections: primary and secondary data sources, especially SharePoint lists.
  • Media: images, logos, and picture buttons found in the package.
  • Warnings: anything that can affect export quality or require manual rebuild work.

When to stop and inspect

Stop before Required Settings if the view count is clearly wrong, if no primary SharePoint data source is detected, if key fields are missing, or if most rules are marked as script/manual review.

The earlier you catch a bad source package, the less time you spend mapping the wrong columns or validating a package that was built from stale source files.

What good looks like

  • The form name and source file look correct.
  • The view list matches the InfoPath design, or a single-view show/hide form is split into expected virtual screens.
  • The primary SharePoint list or library is visible in Connections.
  • Warnings are explainable and small enough for builder review.

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