Context Sensitive List Search Broken by August 2015 CU

SharePoint Libraries include a search box for that specific library, e.g.:


Prior to the August 2015 Cumulative Update, it was possible to find an item within the specific folder of a library. In the above example, if you went into Subfolder and then searched for an item, the search would be limited to items within that subfolder. After the August 2015 CU has been applied, the search box is no longer context sensitive. All items will be returned from the library that match the specific search term.

This is due to a change in the file INPLVIEW.js (and INPLVIEW.debug.js) where a function call was dropped which prevents the context sensitive search from working. As a temporary workaround, it is possible to modify these files to get this search functionality to it’s original state.

The first thing that needs to be done is to make copies of INPLVIEW.js and INPLVIEW.debug.js, which are located in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\LAYOUTS. These copies must be restored prior to installing a SharePoint patch, otherwise the files may not be updated by a patch.

Next, in INPLVIEW.debug.js, open the file with a text editor and go to line 3058. This line will be within the function named “HandleRefreshViewInternal”. Line 3058 should not have any text. Add the text:

url = FixUrlFromClvp2(clvp, url, false);

For INPLVIEW.js, find the text var b=c.ctx.queryString,a=c.ctx;. Immediately after that text, add:

b = FixUrlFromClvp2(a, b, false);

For INPLVIEW.debug.js, the entire function will look like:

function HandleRefreshViewInternal(clvp) {
    var url = clvp.ctx.queryString;
    var ctxObj = clvp.ctx;
    url = FixUrlFromClvp2(clvp, url, false);
    if (typeof ctxObj.searchTerm != "undefined" && ctxObj.searchTerm != null)
        url = RemovePagingArgs(url);
    if (ctxObj == null || !ctxObj.IsClientRendering) {

And for INPLVIEW.js:

HandleRefreshViewInternal(c){var b=c.ctx.queryString,a=c.ctx;b = FixUrlFromClvp2(a, b, false);if(typeof a.searchTerm!="undefined"&&a.searchTerm!=null)b=RemovePagingArgs(b);if(a==null||!a.IsClientRendering){SubmitFormPost(b);return}c.RefreshPaging(b)}

There is a PSS case open for this issue to revert the change back to pre-August 2015 CU behavior.

Trevor Seward is a Microsoft Office Apps and Services MVP who specializes in SharePoint Server administration, hybrid scenarios, and SharePoint Online. He has been working with SharePoint for 16 years from SharePoint 2003 on up, managing environments with terabytes of content for 150,000+ user organizations. Trevor is an author of Deploying SharePoint 2016 and Deploying SharePoint 2019. You can find him on Twitter and in /r/sharepoint.