Forum Discussion
LVT suddenly more picky: several views suddenly not working anymore
I would gladly try to help through a MS Teams meeting if interested.
- In my case, I have content types for documents and document sets, my index are properly set up and my views only filter and sort through the indexed columns. I showed it all to Marc Anderson and he confirmed the issue but was not able to get the attention of Microsoft with it. You are very welcome to take a look. I have several setup like this at different clients: One doc lib with doc sets and flat views on documents that don't work anymore.
- I spoke to Shawn recently. My recommendation is to separate the data into multiple document libraries. If you still want to access them all from a single view, it is doable by either create a page with short links to the different document libraries. Or you could include them in the same library, by adding them as a shortcut link.
The advantage of having multiple document libraries is that you could actually handle them in a more complex way. Exclude some of them from search, set specific retention policies or even hide certain document libraries from end-users.There are several issues that I find with this idea of splitting into multiple libraries:
-There may not be an obvious criteria to split the library, then having multiple is a nuisance on the user point of view. I have several real-life scenarios that I can share: HR employee files (one doc set per employee) where one would like to filter all the performance reviews, several suppliers (one doc set per supplier) on a big project where one would like to filter some document types, Contract projects where lawyers would want to filter the documents assigned to them transversally.
-The split-library solution gets a lot more complex to assemble: site content types, library templates, some tricks to aggregate unified views... Compare that to a single library which can be assembled by a power user or for significantly less consulting costs.
-From the user point of view, working in a single library interface may also be much simpler: all the views they need, direct interactions with documents and metadata. For some existing clients, I was forced to recreate key views using the PNP Modern Search but it is much less usable than a basic view in this scenario.
-The deal with Microsoft has always been that a library supports 30M documents and if you do your indexes correctly, you won't have any issue. I did that and it worked well until it didn't in 2022 for libraries with doc sets. Several clients with which I did not even work anymore suddenly had their libraries failed.
For new projects where I need to implement the pattern, I resorted to create a separate "archive" library to move all the inactive document sets. If volume allows, it leaves less than 5000 active documents and doc sets in the "active" library and I created a Power Automate flow to move the doc sets once they are completed. It adds complexity to my ideal pre-2022 scenario, but keep a lot of advantages.
Hi ArefHalmstrand! Thanks so much for reaching out. I have not considered separate content types. I have tried to limit views and index columns. I would be interested in a MS Teams call if you have the time. Please private message me for contact details.
Cc Francis Laurin , thanks for your reply yesterday. I appreciate your follow up.
