I have never seen this behavior before. I have a user with a hosted feature service whereby the permit type field shows a lock on the data table (figure OCP_1), but the field is editable (figure OCP_2), and the settings allow for Add, update and delete features (figure OCP_3). Additionally, it is possible to edit the feature within the web map.
There is a relationship class / related table, but the primary key is based on permit id and not permit type. I don't have any details about how the feature service was published. My next step is to download and attempt to publish a new service --- I don't want to overwrite at this point.
Has anyone else encountered this issue where the field is locked in the data table, but is editable within a web map?
