SharePoint / SharePoint/sp-dev-docs

SharePoint list form JSON: "enabled": false / "readOnly": true - does not make field read-only (field still editable)

Open
#10,827 4 comments 0 reactions 1 assignee View on GitHub

@Ashlesha-MSFT is already working on this.

Since May 13, 2026.

area:list-formatting Needs: Author Feedback sharepoint-developer-support type:bug-confirmed
Dominant language
PowerShell
Stars
1.4k
Forks
1.1k
Avg merge
4d 12h
Merged PRs (30d)
12

Description

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

Declarative list formatting

Developer environment

None

What browser(s) / client(s) have you tested
  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)
Additional environment details

No response

Describe the bug / error

Hi,
I am experiencing an issue with SharePoint list form customization using JSON. A field configured as disabled ("enabled": false / "readOnly": true) is still editable in the form UI.

Environment:
SharePoint Online
List form customization using JSON (Configure layout)
Standard SharePoint form (no SPFx extension)

Problem description:
I am trying to make the field CzynnoscRW read-only (disabled) using fieldSettings. However, despite setting "enabled": false / "readOnly": true, the field remains editable in the form.

JSON configuration used:
{
"sections": [
{
"displayname": "Szczegóły zadania",
"fields": [
"SzczegolyZadania",
"Miejsce",
"MiejsceKomasacja",
"MiejsceZwrot",
"Czynnosc",
"CzynnoscRW",
"CzynnoscWydanie",
"Dok"
]
},
{
"sections": [{}],
"fieldSettings": [
{
"name": "CzynnoscRW",
"enabled": false
}
]
}
]
}

Steps to reproduce

Open SharePoint list
Go to Configure layout → Body
Apply the above JSON
Open item form (New/Edit)
Try to edit CzynnoscRW

Expected behavior

Expected behavior:
The field CzynnoscRW should be disabled (read-only) and not editable.

Actual behavior:
The field is still editable.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.