Builder review7 min readUpdated June 5, 2026

How to use Optional Settings for field mapping review

Review included fields, override target columns, exclude noise, and leave builder notes before export.

Quick answer

In short

Optional Settings is a review step. Use it to fix field mappings and builder notes, not to re-enter the basic SharePoint target information.

Most likely cause

Messy output usually comes from leaving internal-name matches unreviewed when the InfoPath label and SharePoint column are similar but not identical.

What to do next

Filter to Needs review and Unmapped first. Fix those rows before adjusting lower-risk mapped rows.

What to review first

  • Rows marked Needs review, Unmapped, Manual, or Override.
  • Dropdowns that depend on secondary lists.
  • Boolean fields that came from InfoPath checkboxes.
  • Person-like fields that may need email, display name, or claims behavior.
  • Fields with repeated or generic captions, such as multiple optional sections.

When to use override

Use a mapping override when Form Migrator picked the wrong SharePoint column or when two possible matches are close enough that the generator should not guess. The override should change only the target column, control type, required behavior, or builder note. Do not rename the source InfoPath binding.

When to exclude a field

  • The field is a hidden state flag used only by old InfoPath show/hide logic.
  • The field is a duplicate caption or unbound label.
  • The field belongs to a secondary list screen that will be rebuilt separately.
  • The target SharePoint list no longer stores that value.

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