Deprecated: YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container::__construct(): Implicitly marking parameter $parameterBag as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php on line 60
Deprecated: YoastSEO_Vendor\League\OAuth2\Client\Provider\AbstractProvider::authorize(): Implicitly marking parameter $redirectHandler as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/league/oauth2-client/src/Provider/AbstractProvider.php on line 416
Deprecated: YoastSEO_Vendor\GuzzleHttp\Client::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/Client.php on line 181
Deprecated: YoastSEO_Vendor\GuzzleHttp\ClientInterface::getConfig(): Implicitly marking parameter $option as nullable is deprecated, the explicit nullable type must be used instead in /home/nubelus/sharedove/adisjugo/wp-content/plugins/wordpress-seo/vendor_prefixed/guzzlehttp/guzzle/src/ClientInterface.php on line 77
{"id":444,"date":"2011-08-13T21:22:41","date_gmt":"2011-08-13T19:22:41","guid":{"rendered":"https:\/\/blog.sharedove.com\/adisjugo\/?p=444"},"modified":"2011-08-13T21:22:41","modified_gmt":"2011-08-13T19:22:41","slug":"combine-list-view-and-caml-query-string-in-spquery","status":"publish","type":"post","link":"https:\/\/blog.sharedove.com\/adisjugo\/index.php\/2011\/08\/13\/combine-list-view-and-caml-query-string-in-spquery\/","title":{"rendered":"Combine List View and CAML Query string in SPQuery"},"content":{"rendered":"There is a need sometimes to combine a physical list view (on a SharePoint list) with a custom CAML query when retrieving the data in the SharePoint object model. Most of you probably know that there is an overload of the SPList.GetItems() method which takes a SPQuery and a View Guid as the parameters, but most of the time you don’t know the Guid of the View on the target system, and honestly, you nether want to store it to the configuration list, nor to search for it in the code.<\/p>\n
Luckily, there is a (not so obvious) way to do it through the SPQuery, and then to pass only the SPQuery to the GetItems() method:<\/p>\n
\n\nstring query = "<Where><Eq><FieldRef Name="ID" \/><Value Type="Counter">1<\/Value><\/Eq><\/Where>";\n\nSPList citiesList = web.Lists["MyList"];\n\nSPView view = citiesList.Views["MyView"];\n\nSPQuery qry = new SPQuery(view);\n\nqry.Query = query;\n\nSPListItemCollection items = citiesList.GetItems(qry);\n\n<\/pre>\nIn this example, a SPListItem with ID 1 will be returned from the “MyList” (note the CAML query), but only the fields which are defined by the view “MyView” will be in the\u00a0result set. Quite usefull.<\/p>\n
PS. Note how the GetItem() method parameter is called “viewName”, even if they really wanted to say “View Guid”. Oh, what the heck, name, guid, id, whatever, all the same in the SharePoint world. You just have to love Microsoft for this one… \ud83d\ude09
\nhttp:\/\/msdn.microsoft.com\/en-us\/library\/ms434064.aspx<\/a><\/p>\n\n\t\t\t
\n\t\t\t <\/div><\/div>\n\t\t