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

Rich text, plain text, and read-only fields

Handle InfoPath controls that look like labels but are actually bound to source data.

Quick answer

In short

A PlainText control with a binding is a field, not just a label. A label without a binding is visual text and should not become a data card.

Most likely cause

Single-view show/hide forms often use plain text controls for detail screens, causing early generators to show labels without editable fields.

What to do next

Check whether the control has a binding. Bound controls should be mapped or rendered; unbound captions should usually stay as labels or be suppressed when duplicate.

How to tell the difference

  • Bound plain text: reads from an InfoPath field and may need a Power Apps label or read-only value control.
  • Unbound label: static caption or instruction from the layout.
  • Rich text: may need a rich text editor, HTML display, or plain text fallback depending on target column type.

Builder decision

Do not convert every caption into a standalone field. Use the source binding and mapping table to decide what should save to SharePoint and what should exist only as screen text.

When output looks label-only

If a generated screen shows many captions but no editable controls, check whether the source fields were bound plain text controls, whether they were mapped to the primary target, and whether they belong to a secondary-list screen that needs a separate data pattern.

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

Views8 min read

Single-view show/hide forms and virtual screens

Handle InfoPath forms that have one view but use rules to show and hide many sections.

Analyze7 min read

InfoPath source fields vs SharePoint columns

Understand why source bindings, user-facing labels, display names, and internal column names can all be different.

Start7 min read

How to use Optional Settings for field mapping review

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