| Prior to the December 2011 CU, the "Newsletter (no lines)" style in a list view did not display the column headers. After the December 2011 CU was applied, it added the column headers. There is no way around this, unless you use a dataview web part (which cannot be done on publishing sites).
|
| In SharePoint 2010, a Search Center's results page can display a refinement panel. This panel allows the user to filter the results based on other criteria the categories that are displayed. By default, the refinement panel shows these categories:
- Results Type
- Site
- Author
- Modified Date
I didn't want to see Author or Modified Date categories. Also, the Site category shows the root site. It doesn't display the actual sites under the root collection, nor other collections that are attached to that root site. I wanted to be able to see the actual site names.
Here we go...
To remove the Author and Modified Date categories:
- Open the page in edit mode.
- Open the web part properties pane.
- In the Refinement section, uncheck Use Default Configuration.
- In the Refinement section, under Filter Category Definition, open the XML.
Note: You may want to copy and paste this into Visual Studio for XML formatting.
- Delete the code that starts with <Category Title="Author" and end it with /> which is just before the ending </FilterCategories> tag. Click here for a screenshot of the entire code.
- Click OK to save the XML.
- Click Apply to apply the web part changes.
- Click OK to save the web part changes.
- The categories should now be removed from the refinement panel.
Change the Site Category to Display All Sites
What we really need to do is to display the Site Title property and not the Site Name property.
- Back in the Refinement Panel, Filter Category Definition XML, locate the Site category. It will start with <Category Title="Site" Description="Which site this document is from".
- Change MappedProperty="SiteName" to "SiteTitle" (no spaces).
- Click OK to save the XML.
- Click Apply to apply the web part changes.
- Click OK to save the web part changes.
- All sites should now appear in the Site category (if you have results and it depends on the max number filters to display).
But, we're not done yet! If you test clicking on one of these sites to filter your results, you will get the lovely, "We did not find any results for..." error. My personal SharePoint consultant (not really, but I think he is), Adam Preston, gave the answer. We must allow this property to be available in scopes. By default, it's not. Silly SharePoint!
- From Central Adminsitration, access your Search service.
- From the Quick Launch, under the Queries and Results section, click Metadata Properties.
- Navigate to and locate SiteTitle. (Click here for a screenshot of how SiteTitle is listed.)
- Edit the properties of SiteTitle.
- In the Use in scopes section, check Allow this property to be used in scopes. (Click here for a screenshot.
- Click OK to save your changes.
- Perform a full crawl on your content source.
Poof! The refinement panel now filters and displays results!
Here's a great blog post about the refinement panel options that helped me with these changes:
http://www.sharepointanalysthq.com/2010/06/sharepoint-2010-search-refinement-panel-options/
Here's how to show item counts on the filters:
http://www.sharepointanalysthq.com/2010/06/showing-items-counts-in-sharepoint-2010-search-refiners/ |
| When a user tries to edit a document from the item menu in a document library using "Edit in Microsoft Word" (as an example), the following message can be displayed:
This could be related to a long file name. Have the user save the document locally, rename the file to a shorter name, delete the doc from the library (if possible - will loose versions), and re-upload with new, shorter name. |
| There are certain limits and exceptions when working with SharePoint 2010 content with SharePoint Workspace 2010. Note that the navigation pane of the SharePoint Workspace 2010 displays links to unsupported lists and libraries, which you can conveniently click to work with in SharePoint 2010 for full support if you are online.
Be aware of the following limits and exceptions when working in SharePoint Workspace 2010:
- The total number of files you can store across all your SharePoint workspaces is approximately 10,000.
Note: If you have not updated to Microsoft Office 2010 Service Pack 1, you can only store approximately 500 documents in SharePoint Workspace before you see warning messages about document limits. Additionally, once you exceed 1,800 documents across your SharePoint workspaces, a warning message appears to inform you that only document properties will be downloaded to the workspace.
- Each list can have no more than 30,000 items.
- From within SharePoint Workspace 2010, you can create, update, and delete files in a library and new items in a list, but you cannot create new sites, libraries, and lists.
- Sites based on an Access Web Database template are unsupported.
- The following lists are unsupported: Calendar, Wiki page, and Survey.
- The following views are unsupported: Project Task list in Gantt view, Style, In-line Folders (which show as groups), and Item Limit.
- The people picker control is not supported.
- The editing of site pages in the site pages library is not supported.
- The editing of list attachments is not supported (Although you can open the attachment as read-only).
- The synchronization of changes made to a OneNote notebook is not supported.
- Lists or libraries protected by Information Rights Management (IRM) are not supported.
Source: http://office.microsoft.com/en-us/sharepoint-foundation-help/synchronize-sharepoint-content-with-sharepoint-workspace-HA101854201.aspx |
| You create an external content type to LOB data. When you attempt to view the list in the browser, you get this error:
This can happen with the SQL table has more rows than the default throttle of the BCS.
*Note: "BCS1" is the name of the service application. You will need to change this to your service application name.
Scope : Database
ThrottleType : Items
Enforced : True
Default : 2000
Max : 1000000
Scope : Database
ThrottleType : Items
Enforced : True
Default : 2000
Max : 1000000
Scope : Database
ThrottleType : Items
Enforced : True
Default : 40000
Max : 1000000
PS Y:\>
|
| SharePoint Designer has a "bug" when you create a Data View web part and group on a lookup column. The column does not display as the value, but instead as the href code text.
The fix is to add attribute to the xsl.
Original code was: <xsl:value-of select="$fieldvalue"/>
Changed to: <xsl:value-of select="$fieldvalue" disable-output-escaping="yes" /> |
| Who knew that there are limitations to the number of specific column types you can have in a view? Not me!
By default, you can only use a maximum of eight (8) columns in a view that are of the type workflow status, lookup, or person/group. |
| In our environment, we upgraded from MOSS 2007 to SharePoint 2010, but kept the 2007 look and feel. However, all new sites get the 2010 look and feel. Not a great user experience.
You can change your 2010 site back to the 2007 look and feel by using the following PowerShell commands:
Note: This works on new 2010 sites that were never upgraded. |
| If you want to know which sites reside in a specific content database, run this PowerShell command:
|
|
|
|
|
|