A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
This behavior is not documented as a known issue in the provided references. However, there are a few areas to check based on related SharePoint form and workflow behavior:
- Verify that the list form definition itself is not being replaced or reset by a provisioning process or customization. In SharePoint, list forms are defined by
<Form>elements that specify the URL and type (DisplayForm, EditForm, NewForm). If another solution or customization reprovisions the form (for example, a template, feature, or deployment script), it can effectively reset the form to a default state, which would make fields appear with internal names and lose descriptions.- The form definition is controlled by attributes such as
Type(DisplayForm, EditForm, NewForm),Url, andUseDefaultListFormWebPart. If a form is reprovisioned withUseDefaultListFormWebPart="TRUE", SharePoint can recreate a default ListFormWebPart, which may drop customizations and show internal names.
- The form definition is controlled by attributes such as
- If the list form is customized with Power Apps (SharePointIntegration), confirm that no formulas or lifecycle events are clearing state or resetting controls unexpectedly:
- The default generated form uses
SharePointIntegrationandSharePointForm1with autogenerated formulas forItem,OnNew,OnEdit,OnView, andOnSave. If these formulas are modified incorrectly, the form can show unexpected values or reset fields. - Collection variables in a customized form persist for the entire session and are not automatically reset when the form closes. If collections or variables are used to populate field defaults and are cleared in
OnViewor otherSharePointIntegrationproperties, fields can appear blank when the form opens again. - Imperative functions (such as
Launch()) inSharePointIntegrationproperties can cause unexpected behavior because lifecycle events can trigger in the background even when the form is not visible.
- The default generated form uses
- Confirm that Power Automate flows are not updating list schema or form configuration, only list item data. The documented Power Automate issues around forms primarily concern connector limits, invalid connections, and field/response limits, not schema resets. However, if a flow or another process is modifying list columns (for example, deleting/recreating columns, changing types, or renaming), the form can revert to showing internal names or lose descriptions.
- If workflows (SharePoint 2013 platform) are used in parallel, be aware that certain column types (such as Multiple lines of text with Append Changes) can behave unexpectedly when workflows update list items. While the documented issue is about blank values in workflow output, it illustrates that background updates to list items and status fields can have side effects on how data is stored and displayed.
To reduce the chance of this happening again:
- Lock down schema changes
- Avoid automated changes to list columns (create/delete/rename) from flows or scripts once the form is in use.
- If a provisioning solution is used (site scripts, templates, or custom solutions), ensure it is not reapplying list or form definitions on a schedule.
- If using a Power Apps customized form
- Review
SharePointIntegrationproperties (OnNew,OnEdit,OnView,OnSave,OnCancel) and ensure they only call supported form functions likeNewForm,EditForm,ViewForm,SubmitForm,ResetForm, andRequestHideas documented. - Avoid using
SharePointIntegration.Selecteddirectly for item selection; instead, useSharePointIntegration.SelectedListItemIDwithLookUpas recommended, to ensure the correct item is loaded and not an empty or default record. - Clear or initialize collection variables explicitly in
OnViewor other appropriate events so that stale state does not overwrite visible fields.
- Review
- If the form is not customized with Power Apps
- Check whether any custom solution (SPFx, declarative schema, or feature) is redefining
<Form>elements for the list. If so, ensure it is not being redeployed or updated in a way that resets the form.
- Check whether any custom solution (SPFx, declarative schema, or feature) is redefining
If the issue continues and cannot be tied to a specific customization or automation, collect detailed repro steps (including timestamps and any flows or customizations that ran around that time) and open a support request so that logs can be reviewed.
References: