Sign up / Sign in
Supported6 min readUpdated June 5, 2026

Checkbox and Yes/No field behavior

Make sure InfoPath checkboxes generate as real Power Apps checkbox controls and save Boolean values.

Quick answer

In short

InfoPath checkboxes should become Power Apps Checkbox controls bound to SharePoint Yes/No columns or Boolean-compatible fields.

Most likely cause

If the app shows literal text like false, the field was classified as text instead of a checkbox/Boolean control.

What to do next

Check the mapping control type and the generated card. The value control should be a Checkbox, not a TextInput.

Expected generated behavior

  • Default resolves blank values to false for new forms.
  • Update saves a real Boolean value.
  • The visible control is a checkbox with a label.
  • The SharePoint column is a Yes/No field or a compatible mapped Boolean field.

Common symptoms

  • A black square appears instead of a checkbox.
  • The field displays the word false or true.
  • Clicking the field does not toggle a value.
  • Submit fails because the target column expected Boolean but received text.

Builder review

After import, toggle each generated checkbox and submit a test record. Confirm SharePoint stores Yes/No correctly and that existing records load checked or unchecked as expected.

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

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.

SharePoint6 min read

Import SharePoint columns into mapping

Use real SharePoint column metadata to improve field mappings, control types, required flags, and save formulas.

Fields6 min read

Map user-facing labels without breaking SharePoint saves

Keep friendly labels, InfoPath bindings, and SharePoint internal names in their proper places.