Querystring parameters you should not use in your SharePoint application

re: Querystring parameters you should not use in your SharePoint application

Stefan Goßner — Tue, 24 Apr 2012 15:00:35 GMT

Hi Io,

you can read them - but you should not set these query string parameters.

Cheers,

Stefan

re: Querystring parameters you should not use in your SharePoint application

Io — Tue, 24 Apr 2012 14:26:35 GMT

Mortacci tuaaa!

Yes, but as one reads the parameter from querystring?

re: Querystring parameters you should not use in your SharePoint application

Jeremy — Mon, 05 Dec 2011 17:36:02 GMT

While the question is silly, neither answer is productive.

The key to finding a solution is to recognize that the reserved list must be avoided as the name of the Querystring parameter, yet you are still able to filter against the ID column, for example.

Simply use a "friendly" name for the actual Querystring parameter. If your list is Customers and you want to filter your by the ID field, name your Querystring parameter CustomerId or cid or ... (anything but a name on the reserved word list).

In the configuration of your connection, use ID in the Consumer Field Name. Using this approach, the expected results are achieved consistently.

re: Querystring parameters you should not use in your SharePoint application

Stefan Goßner — Thu, 10 Nov 2011 15:28:03 GMT

Hi Braham,

I doubt that there is enough disk space available world wide to store the list of all allowed query string parameter names.

Cheers,

Stefan

re: Querystring parameters you should not use in your SharePoint application

Brahmam — Thu, 10 Nov 2011 15:24:13 GMT

Is there a definitive list anywhere of the query string parameters that we are allowed to use?

re: Querystring parameters you should not use in your SharePoint application

Stefan Goßner — Sun, 05 Jun 2011 21:19:15 GMT

Hi Adrian,

that is impossible as there is an endless list of allowed query string parameters.

Cheers,

Stefan

re: Querystring parameters you should not use in your SharePoint application

Dr Adrian Colquhoun — Sun, 05 Jun 2011 11:13:36 GMT

Is there a definitive list anywhere of the query string parameters that we are allowed to use?

re: Querystring parameters you should not use in your SharePoint application

Edward Joell — Mon, 06 Dec 2010 19:24:46 GMT

Truly unpredictable. We are used the parameter ID in four or five querystrings sometimes as the first parameter other times as the second or third parameter. We had an issue with only one usage where the any user without Site Collection Admin rights would get an Access Denied error thrown on attempting to open that page. But when the parameter name was changed to ListItemId then the page worked as designed. However none of the other pages with that parameter in the call to open the window responded in that fashion. Truly a model of SharePoint's consistency

re: Querystring parameters you should not use in your SharePoint application

Stefan Goßner — Wed, 26 May 2010 05:37:43 GMT

Hi Vertigo,

as indicated these parameters are reserved and internally used for a special purpose.

E.g. the ID parameter is undergoing a string-to-int conversion to map it to a list item ID.

If this parameter now contain non-numeric values this string-to-int conversion will fail and you will get an exception.

Using any of these parameters in your code can lead to unpredictable results.

Cheers,

Stefan

re: Querystring parameters you should not use in your SharePoint application

Vertigo Hopes — Wed, 26 May 2010 04:00:07 GMT

I noticed that when I used the ID parameter in the query string, it would work for numbers but not letters. ?ID=1234 would render correctly, but ?ID=123A causes the page to crash. Any ideas? I'm using SharePoint 2010 and a query string filter web part to filter a document library web part.