Supported6 min readUpdated June 5, 2026

Map user-facing labels without breaking SharePoint saves

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

Quick answer

In short

Use friendly labels for what users see. Use SharePoint internal names for DataField, Update, and submit behavior.

Most likely cause

A generated label that looks like DirofEasements or StateConservationist is a display cleanup issue. A DataField changed to Director of Easements is a save-breaking issue.

What to do next

Correct the user-facing label, but leave the target SharePoint internal column binding intact.

Correct separation

Label text: visible field caption on the app screen.
DataField: SharePoint internal column name.
Update: Power Apps value saved to that internal column.
Default: value loaded from the record for that internal column.

Why this matters

Power Apps binds SharePoint data cards by the internal column key. User-facing labels can be changed freely, but changing internal bindings to friendlier names can break form submit or create fields that never save.

Review after import

Select the DataCard label and check its Text property.
Select the DataCard and check DataField.
Confirm the Update property references the correct control value.
Submit a test item and verify the SharePoint column receives the expected value.

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

Analyze7 min read