0

I am facing this strange and UN-logical behavior inside our custom list view. now we have a sharepoint enterprise farm 2013. and the list threshold for the web application is set to the defualt which is 5,000. but i am facing this scenario:-

  1. I have added the "Created By" column inside the Index columns for the custom list.
  2. I defined a list view which will show items that were created by the "System Account" and sort items using the Id, as follow:- enter image description here
  3. then using the site admin, i accessed the list view and i can view all items which equal to 2949, as follow :-

enter image description here

4. so now since i am filtering using an Indexed column (Created By) + i am sorting using the ID + the total number of items = 2949, so i were assuming that end users will be able to access the list view, but when they do so they got threshold exception, as follow:- enter image description here

So can anyone advice on this please?

note. now we have another Indexed columns named "Alert Period in month" of type number, and i define another view with this filter/sort:- enter image description here

and the number of items on the view will be equal to 350, and end users were able to access this list view.. so is the issue i am facing on my first list view is with the Indexed column (created-by) OR the problem with the number of item which is 2949, although it is below the threshold which is 5,000??

  • 1
    Can you guess the total number of records in the list? You may need to wait for the indexing job to finish depending on the number of records. – Ahmad Zia Feb 27 at 6:43
  • @AhmadZia the list contain 6350 items and i run a full crawl twice , but did not fix the issues.. also i did an index reset and run another full crawl without any positive results... – SharePoint TestDev Feb 27 at 12:28
  • It appears that its a known issue with "Created By" indexed column social.technet.microsoft.com/Forums/ie/en-US/… unless someone has a solution or work around. – Ahmad Zia Feb 28 at 5:01
  • @AhmadZia looks from the link that this problem is happening inside sharepoint 2010, and it did not get fixed till now on sharepoint 2013 !!!! – SharePoint TestDev Feb 28 at 12:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.