Honor read-only fields in the attribute table (Experience Builder)

[Bud]

In the web map form configuration, I've defined select fields as being read-only.

The read-only fields are honored in the editor widget, but not in the attribute table; all fields are editable in the attribute table.

This idea is to honor read-only fields in the attribute table.

[KenBuja]

Do you own the layer that you're editing? If so, you will be able to edit all fields regardless of how you set their read-only status. You should test this with another account.

[Neal_t_k]

@KenBuja, @Bud I did some minimal testing but this appears to lock it down even for owners:

In AGOL go to the data tab, click fields, select the field you want to restrict and disable editing. 

Looks like it just applies to AGOL Host Feature Services.

[DougBrowning]

Yes forms only block forms from editing. You can get around it in the table or Pro or even a new map.  You have to set at the service level as posted to be safe.  Or if its just for this app make a Hosted View then config editing and use that view for your app then you can still edit the original on the backend if needed.