Column 'Modified' is Read Only (SharePoint)Error Example:Column 'Modified' is read only. Cause:This error generally happens if the account used to target SharePoint is NOT a site administrator (or has sufficiently high permissions, like full control) and tries to update the system field 'Modified'. A more interesting version of this appears if the user has KeepBoth enabled with SharePoint as the "losing" side. When it detects the conflict and tries to create the copied file per the KeepBoth feature, it throws this error as the user doesn't have sufficient permissions to update/add that field value. If this happens, you'll see the error during the change detection step, which is where the conflicts will be detected, in the trace log, like this: 5/30/2020 02:40:20 Layer2.Data.Synchronization.Service Trace The change-detection field 'Modified' on table 'Local_File_Server' has been changed from '1/26/2017 9:04:47 AM' to '3/27/2020 1:37:51 PM' Resolution/Workaround:The user account given in the connection string to access SharePoint either needs additional permissions to the site or must be changed to a user that does have sufficient permissions. This applies to both versions of the error presented in the Cause section. If you are running into this issue even with an admin account, it may also require that “AddAndCustomizePages” permission has been enabled for the account. You can verify this by testing the permissions of the account with the option in the list settings in SharePoint. If “AddAndCustomizePages” has explicitly denied permissions, you need to enable that to be able to write to those system fields. See Allow or prevent custom script on Office Support that explains how to enable this setting.
|
Column 'Modified' is Read Only (SharePoint)
