Wednesday, June 28, 2017

SharePoint Large list issue, View does not work even after do data archival to meet the threshold limit for query criteria

SharePoint has resource throttles and limits that govern the amount of data and throughput that can be managed. The List View Threshold is by default, approximately 5000 items, and is set to allow users to work with large lists, but keep good performance.

Index and Filter views , Using folders to organize using document center site are the some of the workaround you can do to keep your queries within the limit.

As a last choice, with Server versions of SharePoint, is to change the limit. But this is not recommended , since a larger limit increases the possibility of affecting the performance for some or all users. 

Archiving the list is the widely using mechanism to over come this issue. However it is noticed that once the issue occur, even after you archive the list and make count of document less than the threshold limit for the query items, it does not work. This is because the old count is still using by the SharePoint process and it does not refresh. As a workaround on this issue, create a new list and move entire data to the list. You can find in the new list, views are started working.






Nintex Support Interaction - move item from a Document library folder to its root folder.


In Nintex workflow , Please let me know how can I move item from a Document library folder to its root folder.

Moving to sub folder , I have used update item and update name as foldername/filename. It works.
But how to move from subfolder to root ? update name with /filename does not work.


Do you have any other way to achieve it?

(JUN 2017)

In it's current state, Nintex Workflow does not have an action that will move or copy an item from a subfolder to the root.  The copy item action copies files to the root of a list/library, but cannot access subfolders.  I'm going to do some additional research tomorrow to see if there are any web services you can call to achieve the desired outcome.  If I can't find anything, I'll check with our senior engineers to see if they have any other thoughts regarding this.  In the meantime, let me know if you have any questions.
----------------------------------------------------------------------------------------------------------------
I want change what I sent yesterday, since we do have an action that can perform this task, although it's probably not the most ideal solution.  You can create a simple workflow that has the "Copy to SharePoint" action and select the location of the root folder.  Publish the workflow like this, then you can navigate to the file you want to move to root, click on the ellipsis (...) then click on the next ellipsis, click on Workflows, and run the workflow you created.  This will move the document from it's current location to the root (or wherever you specify).  Let me know if you have any questions.

By using copy to SharePoint, we can copy the file to root and can delete the original one. But by this approach, we lose all version history details. Is there any way to move file too root by keeping the version history?

Nintex Workflow does not have an action that will automatically do this for you.  However, what you are requesting is possible when using the "Call Web Service" action and utilizing 'author.dll'.  As this type of request will fall under a professional services offering, we can't offer much additional support, however please take a look at this blog post from one of our Technical Evangelists:


Let me know if you have any questions.