SharePoint list filtering, address bar options

Foreword

• Available list of SharePoint Foundation 2010;
• The number of list items exceeds threshold values ​​(throttling);
• Indexed fields in assortment;
• Views are implemented so that the number of elements does not exceed the threshold and are filtered by index;
• Everything would be fine, but the ability to use built-in filters is still blocked, in addition, the deployment of solutions for the farm is prohibited by organization policies or other conditions.

What to do? Below, under the cut, a number of useful parameters for the address line of SharePoint lists, which can partially save the situation.

Solution options

In fact, there are several options for solving the problem:

• Using search services (if possible) is not particularly convenient since partly, the usual logic of user work with lists will be violated;
• Using the Access table view can be difficult because It’s not always correct to put all fields into the view that this view will require; it’s not always possible for users to be allowed to make table changes to the list;
• Export data to Excel / Access - piecewise solves the search problem by filtering, but as necessary, changing the data is again a trap.
• To make a client solution that would pull up data in pieces and “juggle” with platform limitations - the complexity of the development may turn out to be more than possible, and it will also result in the loss of already existing user experience with lists. Again, we proceed from the fact that we can not do anything on the server.

These options in the context of the production are not entirely appropriate, it can be simpler.
And here we come to the essence of this post. Enumerating the possibilities of filtering lists by regular means due to the address bar parameters.

List Address Bar Parameters

1. The most obvious - View - opens a list with a view whose GUID is passed to the parameter.

Example: /Lists/BigList/AllItems.aspx? View = {50AEF4A1-28AD-4114-A074-C72A0FFCA785}

2. FilterField , FilterValue - a pair of parameters for specifying the attribute (internal name of the filtered field) and its exact value.

The number of pairs of parameter data can be unlimited, the main thing is that the FilterField index coincides with the FilterValue index.
The index in this case is the number. For example, FilterField1 = ... FilterValue1 = ... FilterField7777 = ... FilterValue7777 = ...
If 2 or more different FilterField take the same value, the last one will be relevant, and the previous one will be ignored.

Example: /Lists/BigList/AllItems.aspx?View={50AEF4A1-28AD-4114-A074-C72A0FFCA785► & FilterField1 = Status & FilterValue1 = New & FilterField2 = Author & FilterValue2 = <name of initiator>

3. SortField , SortDir - sort. SortField = <Internal field name> & SortDir = <Sort Order, Desc / Asc>

So far, it's pretty obvious and easy to find on the same technet , but we want more. And partly there is more.

4. We want to filter the fields not only by strict coincidence.

FilterOp - overrides the default comparison (exact match - Eq). It comes with FilterField, FilterValue.
Can apply comparison values ​​from CAML:

• Neq - not equal;
• Contains - contains;
• BeginsWith - starts with;
• Lt, Leq - less, less equal;
• Gt, Geq - more, more equal;
• etc.

Example: /Lists/BigList/AllItems.aspx?View={50AEF4A1-28AD-4114-A074-C72A0FFCA785►&FilterField12=NumAccount&FilterValue12=087& FilterOp12 = Contains Fly in the

ointment - if you need to filter, for example, 12. .2013, then, alas, it will not succeed. Because attribute filtering with the maximum index will be involved. You can of course have the same date attribute for the 2 attributes, but this is already aesthetically not at all beautiful, although it is possible.

5. We want to compare the attribute value with multiple variants.

FilterName , FilterMultiValue - to help us: FilterName - takes the value of the internal name of the field, FilterMultiValue - gets a list of values ​​separated by ";".

Example: /Lists/BigList/AllItems.aspx?View={50AEF4A1-28AD-4114-A074-C72A0FFCA785}& FilterName = ID & FilterMultiValue = 15460; 15459; 15458

True, filtering 2 different attributes by multiple values ​​will fail again. It is necessary to combine the dynamic filter and the filter inside the view.

I hope the information will be helpful. Because it’s not easy to find out about the presence of some of the parameters.