Planning5 min readUpdated June 5, 2026

What to send support for a conversion issue

Send the right source package, screenshots, reports, and expected behavior so a conversion issue can be reproduced quickly.

Quick answer

In short

A good support sample includes the XSN, generated .msapp if available, screenshots of the source and generated behavior, and the exact field/rule/screen that is wrong.

Most likely cause

Support delays happen when the issue is described only as 'not working' without the source form, generated package, or expected behavior.

What to do next

Send a minimal but complete reproduction: source XSN, destination list assumptions, generated output, field names, and screenshots.

Best support bundle

  • The original XSN package or a sanitized sample that reproduces the issue.
  • The generated .msapp package if export succeeded.
  • Screenshots of the original InfoPath behavior and generated Power Apps behavior.
  • The screen name, field name, dropdown/list name, or rule name involved.
  • A short expected-vs-actual description.
  • Any non-sensitive SharePoint column/list details needed to reproduce the mapping.

Sanitizing sensitive forms

Remove real names, emails, account numbers, and confidential content where possible, but keep the structure intact. The structure is what makes conversion issues reproducible: bindings, schemas, rules, view files, and data source names.

Good issue description

Example: In Section-Approve, the Yes button should navigate back to Section 1 after setting Status to Accepted. In the generated app, the button appears but OnSelect only navigates and does not set Status. Source rule name is Accept, screen is Section-Approve.

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