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

[tomaszholisz-dev]

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.

[Ashlesha-MSFT]

Hello @tomaszholisz-dev
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
If you don’t receive a reply within two working days, please use this escalation form to escalate.

[Ashlesha-MSFT]

@tomaszholisz-dev,
Hi,
I checked the JSON configuration and noticed a couple of issues with the implementation.
According to the latest Microsoft documentation for SharePoint list form customization, the supported syntax for read-only fields is:

{
    "sections": [{}],
    "fieldsettings": [
        {
            "name": "fieldName",
            "readonly": true
        }
    ]
}

In the current configuration:

• enabled:false is not a supported property
• fieldSettings should be fieldsettings
• readOnly should be readonly
• The name property must use the field’s internal name, not the display name

Because of this, SharePoint is ignoring the setting and the field remains editable.

for your reference :

{
 "sections": [
   {
     "displayname": "Szczegóły zadania",
     "fields": [
       "SzczegolyZadania",
       "Miejsce",
       "MiejsceKomasacja",
       "MiejsceZwrot",
       "Czynnosc",
       "CzynnoscRW",
       "CzynnoscWydanie",
       "Dok"
     ]
   }
 ],
 "fieldsettings": [
   {
     "name": "CzynnoscRW",
     "readonly": true
   }
 ]
}

[tomaszholisz-dev]

Hello Ashesha and thank You for support,
I have tested few variants:

1.     {
          "sections": [
              {
                  "fields": [
                      "SzczegolyZadania",
                      "Miejsce",
                      "MiejsceKomasacja",
                      "MiejsceZwrot",
                      "Czynnosc",
                      "CzynnoscRW",
                      "CzynnoscWydanie",
                      "Dok"
                  ]
              }
          ]
      }
   

"CzynnoscRW" field is seen and editable.

2.      {
            "sections": [
                {
                    "fields": [
                        "SzczegolyZadania",
                        "Miejsce",
                        "MiejsceKomasacja",
                        "MiejsceZwrot",
                        "Czynnosc",
                        "CzynnoscRW",
                        "CzynnoscWydanie",
                        "Dok"
             ]
           }
         ],
         "fieldsettings": [
           {
             "name": "CzynnoscRW",
             "readonly": true
           }
         ]
        }
   

"CzynnoscRW" field is not seen.

"CzynnoscRW" field is a choice field.

Similar case has been also in below request
#10724

[Ashlesha-MSFT]

@tomaszholisz-dev,
Thanks for the detailed testing — this helps clarify the behavior.

Based on the current results, I will raise a bug for further investigation due to an inconsistency between the expected documentation behavior and what we are observing in the UI.

Observed behavior in our tenant:

• In Form Edit mode, the field behavior appears inconsistent depending on configuration.
• In Quick Edit / Grid view, even with fieldsettings: { readonly: true }, the field remains editable.
• The field behavior is also inconsistent for Choice-type columns, where applying readonly may not behave as documented.
• Concern:

The documentation states that in “Edit all mode” the field should remain visible but uneditable. However, in our scenario, this is not enforced in grid editing mode, which leads to a mismatch between expected and actual behavior.

I will raise this as a bug for engineering review to confirm:

1. Whether “Edit all mode” includes Quick Edit (grid view) or only form-based editing
2. Whether fieldsettings.readonly is fully supported for Choice fields
3. Whether this is an incomplete implementation or a product limitation

Engineering team can validate the scenarios, and we will update once we receive their confirmation.

Thanks again for your support and testing.