Forum Discussion
Solved
Version History broken in modern SharePoint "Sorry, something went wrong"
Hi all -
We are operating in SharePoint Online, using modern libraries. Versioning is turned on, but every time we click to check the version history on a documents, we are greeted with, "Sorr...
I’m with Caite on this one, I ended up having to re-migrate the content while deliberately making sure absolutely nothing else was migrated beyond the files and their versions. No customized forms/views, no required features, etc.
I'm experiencing the exact same error. Was Support able to resolve?
Turns out to be a little complicated. The library in question was created via a migration of an existing classic library using Sharegate. When the library migrated over, it omitted the default forms (apparently they were custom) - Edit.aspx, New.aspx, etc.
I was told to use SharePoint Designer to simply add these forms to the new modern library, but SPD won't let me do that on modern libraries (it throws an error), and apparently this task is not possible using SharePoint Online.
So end result is that I have to re-migrate all these libraries using brand-new-created-by-hand libraries, which I am not looking forward to. But the core issue is those missing default forms.
We are experiencing the same problem after a ShareGate migration..
Did you solve the problem? If yes, how?After weeks of research and troubleshooting, I just had to rebuild and remigrate my libraries. Supposedly it had something to do with the way my libraries were originally set up, but to this day I've never been able to pinpoint what that issue was. I am not the one who built the original libraries, so I don't know what weird nuance threw everything off.
I do know that attempts to add form types to the new libraries failed in SharePoint Designer, and this was the #1 resolution that people sent my way.
