This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi all,
I am a SP Administrator / Developer working for a fairly big organisation. We recently moved to the 2019 version and as a result of user complaints I have discovered that there seems to be a bug in document libraries. Note that all of what I am about to describe is in CLASSIC experience and within the team site (classic) template.
I have created a fresh document library within a test site collection to double check that the issue is not specific to the libraries where users have reported the problem. The setup where the bug happens is:
And onto the bug itself, in the above scenario if the user attempts to save the properties for the document with text of more than 255 characters in the "Comments" field, which of course triggers a validation error asking the user to reduce the number of characters, the value in the "Assigned person" field vanishes. This happens even for documents that were already saved with a value e.g. it will delete the existing value and if user doesn't notice and then saves correctly, the value is gone!
Has anyone else encountered this issue before and if so, how did they fix it?
According to your description it sounds like a strange behavior. I tested in my lab and everything seems to be fine. After the validation pops up, the person column remains the initial value. Have you tried to update your farm to latest version? If not have a try on it. And please let me the patch you have installed now, I will keep on testing, trying to reproduce this issue.
Hi! Thanks for your reply.
We are patched up to June CU (16.0.10361.12114).
When you are trying to reproduce can I just double check that your library is set up something like this and on classic mode (I used link to document as other content type for this test but libraries where issue originally happened is using different content types than this):
Sorry for being late, I managed to create a new farm with the same build number. Still it works fine in my end. Have a check on your page if there are any scripts working.
Hi again,
Thank you very much for verifying this for me. It is looking more and more likely that there is some kind of client side issue in our network environment rather than the issue being with SP....
I am going to have our systems people investigate that and I will let you know how it goes.
Yes, i also have the same feeling with you. Feel free to reply with any update or further question.
Sorry I provided no further update, our systems / network people don't agree with me that the issue is on their end... I might just need to leave this as an unresolved bug in our environment. Thanks for your support anyway!
Hi, @alchemicdreams , thanks for your update. Still it provides some information about a potential issue. It may bring some help to other community members.
If the response is helpful, please click "Accept Answer" and upvote it.