"The day you stop learning SharePoint is the day you stop using it."

Customizing Refinement Panel

To customize Refinement Panel you need to edit the xml file stored in Filter Category Definition. Before performing the above steps make sure that you have created a new Managed Property in Metadata Properties (to the left panel) of Search Administration and mapped to the crawled property.










Perform a Full Crawl and then perform the below given steps.

1. Right click the Refinement Panel web part and select Edit Web Part.
2. Click on Refinement Option and uncheck ‘Use Default Configuration’ check box. 
3. Select Filter Category Definition box in Refinement Option to open the text editor.
4. Copy the entire contents of the text editor and save into a Notepad as an XML file.
5. Open the XML file in Visual Studio and add the following tag in the file.

<Category Title="Your Filter Category Name"   
Description="This category is about….."    Type="Microsoft.Office.Server.Search.WebControls.ManagedPropertyFilterGenerator”
MetadataThreshold="5"   
NumberOfFiltersToDisplay="4"   
MaxNumberOfFilters="20"   
SortBy="Frequency"   
SortByForMoreFilters="Name"   
SortDirection="Descending"   
SortDirectionForMoreFilters="Ascending"   
ShowMoreLink="True"   
MappedProperty="MappedPropertyName"   
MoreLinkText="show more"   
LessLinkText="show fewer"/>


6. Save the file.
7. Copy the entire content of the saved XML file and replace with the original file in the File Category Definition.
8. Click on Apply button and then click on OK button.

      Below image is an example of custom filter category added in Refinement Panel XML file.


Share:

SharePoint Server 2010 Versions

There are four versions of SharePoint Server 2010:

>> SharePoint Server 2010 Enterprise Client Access License features
For organizations looking to expand their business collaboration platform to enable advanced scenarios. Use the Enterprise capabilities of SharePoint to fully interoperate with external line-of-business applications, Web services, and Microsoft Office client applications; make better decisions with rich data visualization, dashboards, and advanced analytics; and build robust forms and workflow-based solutions.

>> SharePoint Server 2010 for Internet Sites, Enterprise
For organizations looking to create customer-facing public internet sites and private extranets using the full enterprise capabilities of SharePoint. This provides full SharePoint Enterprise functionality and no other technical limits.

>> SharePoint Server 2010 Standard Client Access License features

For organizations looking to deploy a business collaboration platform across all types of content. Use the core capabilities of SharePoint to manage content and business processes, find and share information and expertise, and simplify how people work together across organizational boundaries.

>> SharePoint Server 2010 for Internet Sites, Standard
For small and mid-sized organizations looking to create public Internet sites or basic extranets using the Standard features of SharePoint Server 2010.
Share:

Return the Current Site in an Event Receiver; the site in which event occurred.

In an ItemUpdated Event Receiver we were accessing two custom lists for reading values and for that we required to return the current site in which the event occured.
Simply writing SPSite mySite = new SPSite("http://yoursitename"); does not make sense. Because you might don’t know where you need to deploy the Event Receiver, hence hard-coding the Site URL is a bad practice. The below code shows how to return current site URL.

namespace ItemUpdateFeatureReceiver
{
 public class Class1 : SPItemEventReceiver
 {
  private SPWeb _web;

  public SPWeb myWeb
  {
    get
    {
      return _web;
    }
    set
    {
      _web = value;
    }
  }

//Property that returns a custom list named “Document Type”
public SPList CustomList1
{
  get
  {
    SPList myList = myWeb.Lists["Document Type"];
    return myList;
  }
}

//Property that returns a custom list named “Document Sub-Type”
public SPList CustomList2
{
  get
  {
    SPList myList = myWeb.Lists["Document Sub-Type"];
    return myList;
  }
}


public override void ItemUpdated(SPItemEventProperties properties)
{
  //Returns the current site in which event occured
 
  myWeb = properties.OpenWeb();
  
  //your code
}
Share:

When working with Document Panel Properties in Microsoft Word, better check out the “Look Up” field

If you have restored a site/site collection to new site/site collection and you are working with Quick Parts in Microsoft then beware of the Look Up fields. Look Up fields will not display values in your new restored site unless you delete it and create it once again. This is because the look up field internally stores the GUID of the list to which it looks up for values and when the site is restored to a new site/site collection and you look for values in document panel properties in MS Word, you find it blank.

Solution: You need to simply create new look up field(s) with the same name as previous ones and yeah you are done. !! Keep the name of the new Look Up fields same you may have referred your custom SharePoint Designer Workflow, code behind or somewhere else.

Share:

Restoring a SharePoint Site from Enterprise Edition to Standard Edition

We took a backup of MOSS 2007 (Enterprise Edition) site using SharePoint Designer 2007 and tried to restore it to a blank site (Standard Edition). At first attempt we failed to restore it because of an error – “Feature not available: Data Connection Library.” Data Connection Library is not a part of MOSS Standard Edition, it is a part of Enterprise Edition but you can install Data Connection Library to a MOSS Standard Edition.

Here are the steps to install Data Connection Library in MOSS Standard Edition:-

1.  Go to – “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES”
2.  If DataConnectiontionLibrary forlder exist then follow the below given steps.
3.  Open command prompt and run the script –
      stsadm -o installfeature  -name DataConnectionLibrary
    stsadm -o activatefeature -name DataConnectionLibrary

      and you are done…!!!

Missing IWConvertedForms

      At second attempt we again failed to restore the site because of another error –“Missing 10102 ListTemplateID.” We worked out on this and found out that 10102 is nothing but IWConvertedForms. There are two alternatives to deal with this problem. First is to simply delete the IWConvertedForms from SharePoint Designer 2007 or execute PowerShell Script in command prompt as done for the Data Connection Library.

You may execute the same stsadm command (as mentioned above) for any feature
missing in standard edition or you may opt to delete that particular feature as we
did for IWConvertedForms feature.

Hope this article helps you and solve your exceptions.
    
Best Regards !!!
Share:

Author's Profile

My photo
India
A SharePoint Enthusiast working as a Project Lead for an IT Software & Consulting Company in Mumbai. I believe in giving back to the community through which I also learn and develop and eventually grow as an individual and professional. This blog is a small contribution to the community where I live in and may help someone who is seeking knowledge like me. Apart from being a SharePoint Enthusiasts, I am a husband, a father and a blogger. I love to travel and explore new landscapes and meet people of various culture. I am passionate about learning new technology trends in IT. I love spending time on my fitness and have a deep enthusiasm for urdu poetry and career counseling.

Popular Posts

Powered by Blogger.

Contact Form

Name

Email *

Message *

Total Pageviews