![]() Ultimately, the resolution of this problem will lead to less overall administrative time being wasted on figuring out how to solve this problem, or simply implementing one of the workarounds that Microsoft has provided for a while. The result being an autosave for both the user and the document library. After you do that you will need to wait for your desination library to sync back up to the server in SharePoint. ![]() Once it is put into place, a user will be able to visit a document library and search through any document on the list which has not yet been made read-only, open it up in OneDrive, make some change, and have it automatically sync back to SharePoint. The change itself really is not all that complicated. The change will make life easier for the day to day user. While the consequences of the decision to completely remove what would otherwise be a required field can sometimes be very dire, in most cases this was a frequent issue which needed to be worked around. This long-time issue may have caused users to completely avoid creating metadata columns due to the frustrating nature of this error, which leaves out a much of the advanced and important customization that metadata provided. This error essentially makes having required metadata completely worthless unless the documents were completely flawless and never needed to be changed. Any time a user attempted to modify any document which had required metadata, it would throw an error and be unable to sync back into SharePoint. Before this important change, the user would have to manually enter the document library, go through the settings on the library, and then strip out all required fields on any custom metadata. ![]() ![]() In the past, if a user were to attempt to open a document in OneDrive by selecting it from a document library in SharePoint, and that document had a custom, required metadata column on it, it would be impossible to edit in OneDrive. With this change, these libraries will sync with read/write privileges.” That is the change in Microsoft’s own words, and while it may seem small, it will change how SharePoint users interact with document library columns and document libraries by making them more flexible. The new change, quoted here, mostly refers to a fix for an old issue that has frustrated users for quite some time: “SharePoint has long allowed document libraries to have custom columns with required metadata however, the sync client has only treated these libraries with required columns as read-only.
0 Comments
Leave a Reply. |