Neil Randall
asked on
Recommendations for managing large lists in SharePoint 2010
I have a [Customer Code] list which lists every customer, their address and bank codes.
The list has grown beyond the 5000 (LTH) and users cannot now open it.
As it is not recommended to override he List Threshold Setting of 5000. How would the experts manage this list so that customer records can be quickly found/viewed/edited and new records can be added.
(I was thinking folders A-H, I-P, Q-Z although I prefer to avoid folders in SharePoint as it defeats the meta data capabilities).
At the moment it is just one link on the Quick Launch to the whole Customer Code page (in Data Sheet View).
Note: The whole list will still need to be exported to Excel occasionally, which as the Administrator I can still do (well, until the list reaches 20000!).
Thanks for your time
Neil
The list has grown beyond the 5000 (LTH) and users cannot now open it.
As it is not recommended to override he List Threshold Setting of 5000. How would the experts manage this list so that customer records can be quickly found/viewed/edited and new records can be added.
(I was thinking folders A-H, I-P, Q-Z although I prefer to avoid folders in SharePoint as it defeats the meta data capabilities).
At the moment it is just one link on the Quick Launch to the whole Customer Code page (in Data Sheet View).
Note: The whole list will still need to be exported to Excel occasionally, which as the Administrator I can still do (well, until the list reaches 20000!).
Thanks for your time
Neil
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Users often struggle to work with folders - not finding items or putting them in the wrong place.
When you define your views you'll see that they can ignore folders (view settings page). This can be a good way to slice through the folder structure and use indexed filters instead.
But yes I'd tend to recommend Views over folders. I tend to only use folders to segment permissions. e.g. sub content that only a group of people should see; I'd rather set unique permissions on a container than an item. For threshold it's views or partition the content across libraries in some cases.
When you define your views you'll see that they can ignore folders (view settings page). This can be a good way to slice through the folder structure and use indexed filters instead.
But yes I'd tend to recommend Views over folders. I tend to only use folders to segment permissions. e.g. sub content that only a group of people should see; I'd rather set unique permissions on a container than an item. For threshold it's views or partition the content across libraries in some cases.
ASKER
as a stop gap I created folders in the way you describe views, but I think views would be a much tidier solution.