Sign up / Sign in
Builder review6 min readUpdated June 5, 2026

How to handle Analyze warnings

Use warnings to separate real blockers from normal builder-review notes.

Quick answer

In short

Warnings are not always blockers. They are signals that a specific part of the form needs attention before or after export.

Most likely cause

Most warning confusion comes from treating all warnings equally. Missing primary target information is more urgent than a visual layout warning.

What to do next

Sort warnings into upload problems, SharePoint setup problems, generator limitations, and post-import validation items.

High-priority warnings

  • The primary SharePoint list or library cannot be identified.
  • Key view files or schema files are missing from the package.
  • The form contains custom script or managed-code event handlers.
  • A required supporting data source cannot be resolved.

Normal review warnings

  • Original images may need resizing in Power Apps.
  • Buttons were carried over but complex rules need validation.
  • Repeating sections need a child-list or gallery pattern.
  • People fields need identity behavior review.

How to decide what to fix now

Fix anything that prevents the right data source from being selected before export. Leave visual polish and complex business-rule validation for the post-import builder pass unless the warning says package generation will fail.

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

Start8 min read

How to complete Required Settings correctly

Set the app name, destination SharePoint target, supporting lists, and generation options in the right order.

Rules6 min read

Script and managed-code event handlers

Understand why custom code is flagged and how to plan the Power Apps or Power Automate replacement.

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.