Worked example · Synthetic InfoPath source
Follow one form from source to generated package.
Download the input, inspect the actual analysis, and review the generated files before trying your own form.
This hand-authored fixture uses the InfoPath extracted-source format. It contains no customer data or live connection. The analysis and package below were produced by Form Migrator; this is not a customer migration or an InfoPath Designer export.
Downloads are public. An account is required to run analysis in the app; analysis is free.
What this run establishes
Checked in this example
- Source archive ingestion
- Source hash matches downloaded ZIP
- Three generated field cards
- Cancel formula contains ResetForm and Exit
- Generated package ZIP CRC and JSON structure
Still requires a Power Apps environment
- Power Apps Studio import
- SharePoint connection or save behavior
- Tenant permissions
- Business acceptance testing
Artifact checks were performed October 28, 2026. A generated package and valid archive structure do not establish successful Power Apps Studio import or working business behavior.
01 / Input
A small request form with three fields.
The ZIP contains 4 files: a manifest, schema, view, and empty template. One source view contains a text field, a date field, a checkbox, and a Cancel button.
| Source field | Source type | Observed output |
|---|---|---|
| Title | Text | Generated field card bound to Title |
| NeededBy | Date | Generated field card bound to NeededBy |
| RequiresApproval | Boolean | Generated field card bound to RequiresApproval |
The Cancel rule produced ResetForm(RequestForm); Exit(). This check inspects the generated formula; it does not execute the app.
02 / Analysis
Inspect the report, settings, and warnings.
The downloadable JSON contains the actual ingestion result, destination settings, and migration blueprint used for this run. The destination is the reserved example.invalid domain, with a list named Requests. No SharePoint schema was fetched or validated.
Download actual analysis and settingsTo repeat the analysis, choose InfoPath in the app, select “Try the synthetic InfoPath sample,” then choose “Analyze form.” New product versions can produce different warnings or outputs.
03 / Generated artifact
Review the first-pass package.
The generated .msapp contains 19 files, including controls, Power Apps source, and review metadata. The archive passed CRC checks, and its JSON files parsed successfully.
Download generated example .msappThis fixed example download uses no export credit. Generating a package from your own source in the app uses export credits or eligible plan access.
04 / Builder validation
Complete the checks in your pilot environment.
- Create a test SharePoint list with matching columns, then replace the placeholder target settings.
- Open the package in Power Apps Studio, resolve import issues, and reconnect the real data source.
- Review layout, field types, required fields, and Cancel behavior.
- Implement and test the required save/submit behavior. This fixture does not establish a working submission path.
- Test permissions and representative records, then record the manual changes and acceptance results before rollout.
No tenant import result, save result, time-saving figure, or customer outcome is claimed for this run.
Artifact hashes and generator reference
Generator commit: 324e209eec81516e949435134864f2851696596c
Source ZIP SHA-256: 0e386e1d93dda1b56c729b00e0c7508c4761518de7f6a3d948c19f270878803c
Generated .msapp SHA-256: d90d95b7f2034f2b7df6d85e28c208c22decd36175aa9e4a5030ce8d6dfbdcae
Use the same review process for your own form.
Start with one representative InfoPath or Nintex form. Review detected gaps before purchasing export capacity, and keep a builder involved through import and business testing.
Free account required. Uploaded packages and analysis can be saved; review retention before uploading business material.