Content Web Parts: the sweetest way to view and manage data. An overview of the Content Query Web Part (CQWP) in SharePoint 2010/2013 and the Content Search Web Part (CSWP) in 2013. Examples of each, along with tips and tricks for using each web part.
Who’s here today?New to SharePointExisting Users?Developers?Content Owners?End Users?Decision Makers/PM’s?2010?2007?2003?Here because you love SP?Here because you hate it?
Every business has some kind of data
And most companies have an organized chaos situation
A smart person talked you into organizing you date into a site collectionYou organize that data into a meaningful way for your usersBut what if you need to get data out of this site collection…Sure it could take a few minutes to get information out of each site….but what if….
The CQWP allows you to collect data from each of your sites and put them all together in a meaningful and often visually appealing way…out of the box
Multiple on one pageYou can have multiple dispensers on one page
Custom CQWPOr customize it to make it look really cool. Customizations are outside the scope of this presentation.
User Profile Tokens – You can display information about a user much easier
This is a perfect example of how you can make the same concept in two different ways in SharePointThis can be a mix of some CQWP and some manual editing, or it could easily be all CQWP’s with you add image library and links list Lobbyist
This example shows a smaller firm that has one person managing content. Instead of having 4 different lists to manage, there are 5 different CQWP ‘s that all feed from the same list, but are filtered on different criteria
One Links list for all linksDiscussions displays private and public discussions that you have access to – security trimmed
There were over 400 pages and documents that did not have a published version just two weeks before go live
There were over 300 items with “-“, an incomplete description or a duplicate description in the summary field that is displayed in our custom web part and search results.Validation or unique values were not viable options in this case.
Pay attention to the new fields availablein 2010. Use the question mark next to the “Additional Filters“ label to see the exact wording and how to use it.PageFieldValue – uses the current value of a field on the current page.PageQueryString – allows you to grab the value of a query string in the URL. – this can be used to create a dynamic filter for CQWP, i.e.PageQueryString: fieldnameCould use summary links web part to show categories of items and when click on summary link, the page changes the filter: Good Example/Explanation of this: http://blog.wortell.nl/wortell/faq-with-out-of-the-box-cqwp-in-sharepoint-2010/
Slot = variable declared in XSLT fileSlots are the new way of binding data to the Item Style in the CQWP which is pretty convenient since it saves you from editing hidden CQWP properties like CommonViewFields and DataColumnRenames like you had to in MOSS 2007 in order to include custom fields in your content aggregation.Show example of each styleGroup Styles: Large Text, Small Text, Banded, Centered, Separator, WhitespaceItem Style: Image on Left, Title & Description, Title Only, Title with Background, Bulleted Title, Image on Right; Image on Top; Image on top, Centered; Large title; Image only, clickable; Image only, not clickable; Fixed image size; Title, description and document iconNOTE: Can only group by one and show 3 fields OOB, which is why we customize.
If you have two fields that “appear” the same, look at the drop down.
Allow Connections means that data can be passed between the Web Part in question and other Web Parts on the pageExport Mode: Choosing Non-sensitive data only will strip out any data marked as sensitive, and package the rest for the exportExport Options: - Do Not Allow - Non-Sensitive Information - All DataTitle URL: link to anywhereThe Description input field corresponds directly to the Title in that the text you enter here will also appear upon title mouseover. Textyou enter into this description field are searchableHelp URL: link to help documentationMenu options available in the dropdown are Modeless (the default), Modal, and Navigate: Modeless opens a popup window that allows users to continue working "behind" the popup in other windows while the popup remains open. Modal opens a popup window that users must manually close before they're able to continue working. Navigate doesn't open a popup at all, but navigates directly to the help content by refreshing within the already open window. Catalog Icon Image URL allows you to include a small image (with a maximum size of 16x16 pixels) by including the path to the desired image file in this input field.Title Icon Image URL allows you to add an icon (with the same 16x16-pixel limitation) to the title bar of the Web Part by including the path to the desired image file in this input field.Import Error Message is the message that will be displayed to users if the Web Part fails to render. The default error message, as you can see, is "Cannot import this Web Part," but this input field gives you the ability to customize the error message to suit your needs.The Target Audiences input allows to specify the audience for whom the Web Part will display. NOTE: if the CQWP is embedded in the Page Layout, users will not be able to interact with some of these options
DEFAULT IS RECENTLY CHANGED ITEMS
Don’t restrict results by app = all items available to search – use this carefully.
Site Feature – Office SharePoint Server Publishing if not using Publishing template
Cannot filter by multi-select MMDOnly allow “is equal to”
Found onhttp://blogs.sharepointguys.com/brendon/sharepoint-2007/programming/connecting-the-cqwp-without-changing-itemstyle-xsl/ <webParts><webPartxmlns="http://schemas.microsoft.com/WebPart/v3"><metaData><type name="Microsoft.SharePoint.Publishing.WebControls.ContentByQueryWebPart, Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /><importErrorMessage>Cannot import this Web Part.</importErrorMessage></metaData><data><properties><property name="Title" type="string">Custom XSLT Style Content Query WebPart</property><property name="Description" type="string">Adds other templates to the ItemStyle.xsl</property><property name="ItemXslLink" type="string">/Style Library/XSL Style Sheets/DevCowItemStyle.xsl</property></properties></data></webPart></webParts>
Open your mapped network drive to the Master Page Gallery.Open one of the four folders in the Display Templates folder.Note: The folder you choose depends on the type of display template you want to use. For example, if your site uses cross-site publishing, copy a display template from the Content Web Parts folder. For more information, see Display template reference in SharePoint Server 2013.Copy the HTML file for an existing display template that's similar to what you want. The exact location that you copy the file to does not matter, as long as it is in the Master Page Gallery.Open and modify your copy in an HTML editor.
Author:”John Smith” returns content authored by John SmithAuthor: “John Smith”; Author :”John Smith” ; Author : “john smith” all return items containing John Smith and the term author. Filetype:docxFilename:budget.xlsx from Keyword Query Language (KQL) syntax reference
This error message usually means that you are querying items other than pages. Delete the “URL Path” in the Link field. Sharepoint will automatically generate a new link for you.
“CommonViewFields” – If you need to show more fields, export web part, add more fields here, then uploadWe look for the property called "CommonViewFields". This property makes the web part request additional fields, on top of the "base" ones it asks for out of the box. We can edit this property and specify one additional field to ask for, namely the Body field.<property name="CommonViewFields" type="string">Body_x0020_content, RichHTML</property>There's a few ways you can configure this property but the most common one is "Internal name of field", followed by a comma, followed by the type of the field. If you want more than one, add a semicolon between each pair. Note:OOB Additional Filters does not include “Page Content or “Page Layout” but you can group by them.
A quick way to do show rich text in a field would be to search the file for the text <xsl:value-of select="@Description" /> Add disable-output-escaping="yes"inside the tag, so that the end result is: <xsl:value-of select="@Description" disable-output-escaping="yes" />
Checks to see if there are any items after the current item, if yes, sets div class to allow us to target with css, Otherwise, if it is the last one, display a button