Friday, September 30, 2011

Why i need so much.....SharePoint 2010 Search, Standard Search, Enterprise Search, Fast Search....??

Search in SharePoint 2010 is a really complex feature and can be configured in many different ways and you need few or all of them to fulfill users need.
So let's find out what they can do for us..when implementing in SharePoint....
There’s a couple of different versions of Search in SharePoint 2010:

  • SharePoint Foundation Search ( FREE, FREE, FREE!!!)
    • Site Search Only
    • No non-SharePoint content indexing configuration
  • Microsoft Search Server Express(Integrated with SharePoint 2010
    Foundation)
    • Non-SharePoint content indexing configuration
      available
  • SharePoint Server 2010 Standard Edition Search
    • 100 million items
    • SharePoint content
    • Web site content
    • File share content
    • Exchange public folder content
    • Other database content
    • Enterprise Scale Search
    • Federated Search
    • Mobile Search Experience
    • People and Expertise Search
    • Phonetic and Nickname Search
    • Search Scopes
    • SharePoint 2010 Search Connector Framework
    • SharePoint 2010 Search Connector Framework
  • SharePoint Server 2010 Enterprise Edition Search
    • Contextual Search
    • Extensible Search Platform
    • Extreme Scale Search
    • + All Standard/Foundation/Express Edition Features
  • FAST Search for SharePoint
    • Support for 500 million items.
    • Visual best bets (HTML rendering).
    • Sort on any indexed property.
    • The ability to preview Microsoft Word or Microsoft PowerPoint® documents on
      the results page.
    • Deep refinement showing count by property refinement.
    • The ability to document thumbnails on the results page.
    • FAST search Web Parts.
    • Manual promotion or demotion of specific results.
    • Relevancy profiles to show different results ranking to different
      users.
    • Multilingual search controls.
To Implement FAST for SharePoint 2010 you need:

  • SharePoint server licenses.
    A FAST search server license for any servers running FAST search.
    Enterprise CALs for any users using FAST search.
Search in SharePoint 2010 is a really complex feature and can be configured in many different ways. I made this post to sort out what the different components do.
Cheers

Wednesday, September 28, 2011

Pre-defined Taxonomy Metadata for Microsoft SharePoint Server 2010

Knowledge Management and Social Networking are unleashed, for real this time, with the upcoming new version of Microsoft SharePoint 2010. SharePoint 2010 now fills the big gaps in 2007, with managed taxonomies and folksonomies, expertise finding, content rating, and commenting. Enterprise Metadata Management (EMM) is a new set of features introduced with SharePoint 2010 that enable taxonomists, category managers, and administrators to create and manage terms and sets of terms across the enterprise. You can use managed metadata - a hierarchical collection of centrally managed terms that you can define - as attributes or categories for tagging items and documents with Microsoft SharePoint 2010. Item and document classification helps users to find the information they need much faster, it gives context to the cloud, connect users to social networks, enables a new, hierarchical way to access information – independent of the storage location. It simply saves money.

Pre-defined taxonomies, ready to import in Microsoft SharePoint Server 2010 and into the FREE Microsoft SharePoint Foundation 2010 can be licensed and integrated out-of-the-box into your existing intranet, content management application, knowledge management portal, or any other application that would benefit from the power of a robust taxonomy-based classification or search. The taxonomies are flexible and can be easily customized and modified to address unique organizational requirements. No additional software is required.

Pre-defined Taxonomie Metadata Packages for SharePoint 2010.

Enterprise Taxonomy Starter Package for SharePoint 2010:
  • General Business (Accounting and Finance, Human Resources, Information Technology, Legal, Marketing) 395
Enterprise Taxonomy Packages for SharePoint 2010:
  • Banking, Finance, and Investment ......2532 ..[1526/1006]
  • Contracts ........................................[Q3 2010 Release]
  • Insurance ........................................[Q3 2010 Release]
  • Job Titles .......................................2737 ..[1796/941]
  • Product and Services Life Cycles .......1174 ..[1079/75]
  • Records Retention ............................1050 ..[370/680]
Products and Services Taxonomy Packages for SharePoint 2010:

  • Agriculture and Forestry ....................9913 ..[5157/4756]
  • Automotive ....................................1722 ..[1047/675]
  • Building and Construction ................4296 ..[2400/1896]
  • Business Services ............................859 ..[477/382]
  • Computer/Information Technology ....3514 ..[879/2635]
  • Communications/Telecommunications 1150 ..[414/736]
  • Education and Training ...................1034 ..[503/531]
  • Electrical and Electronics .................1930 ..[1204/726]
  • Environmental ................................3066 ..[1472/1594]
  • Fashion and Apparel ......................2413 ..[804/1609]
  • Food and Beverage ..........................8278 ..[4064/4214]
  • Government ....................................1417 ..[879/536]
  • Educational Services ..............278 ..[155/123]
  • Government Services .............125 ..[71/54]
  • Health Services .....................501 ..[365/136]
  • Public Safety ........................273 ..[120/153]
  • Schools ...............................103 ..[79/24]
  • Social Services ....................137 ..[89/46]
  • Health Care ....................................8570 ..[5839/2731]
  • Home and Garden ...........................3749 ..[2035/1714]
  • Industrial Equipment and Supplies .....8944 ..[4915/4029]
  • Metals ...........................................1399 ..[989/410]
  • Minerals, Mining and Drilling ..............1414 ..[862/552]
  • Office Equipment and Supplies ..........4639 ..[1175/3464]
  • Oil and Gas .....................................1202 ..[834/368]
  • Packaging .........................................567 ..[260/307]
  • Personal Care ..................................1753 ..[1012/741]
  • Plastics and Rubber ..........................1190 ..[636/554]
  • Professional Services ..........................525 ..[303/222]
  • Safety and Security ..........................1842 ..[825/1017]
  • Science and Technology ...................3504 ..[1906/1598]
  • Services .........................................9217 ..[5514/3703]
  • Sports and Recreation .......................2814 ..[1451/1363]
  • Textiles and Leather .........................3182 ..[1511/1671]
  • Toys and Games ................................522 ..[318/204]
  • Travel .............................................1418 ..[900/518]
  • Transportation .................................4003 ..[2302/1701]
Specific Taxonomy Packages for SharePoint 2010:



 

   
http://suneet-sharma.blogspot.com/" id="cse-search-box">
     

       
       
       
       
       
     

   

   
   

Monday, September 26, 2011

SharePoint 2010 Certifications:

Exam 70-573: TS: This is targeted on developing applications to operate inside the software.

Exam 70-576: PRO: This is a bit more comprehensive compared to the 70-573 with additional focus on design.

Exam 70-667: TS: This certification is targeted on the configuring of the software way more than production.

Exam 70-668: PRO: This final exam is made for people who should be managers of the application.

Find out more facts about certifications, in general, head over to http://CertificationsHQ.com.

SharePoint Developer: What new you can do in SharePoint 2010

  1. System requirements for server or developer machine is 64-bit and minimum Dot Net Framework 3.5.
  2. SSP is not longer existing as it used to be there is now Service Applications.
  3. Workflow is now not limited to items or lists.
  4. Development can be done in a client OS (recommended : Windows 7)
  5. Web Parts can be placed without web part zones.
  6. UI Shifts (Ribbons, In Place Editing).
  7. Claims Based authentication is added.
  8. Sandbox Solutions (isolation and resource limitations (memory, SQL, CPU) that allows administrators to let others safely add and consume custom solutions without impacting overall farm performance and stability)
  9. Developer Dashboard (can be enabled on a page to view more information that helps the developer in performance tuning and troubleshooting issues related to page rendering)
New Things in SharePoint Development Platform :

  1. Pages and user interface (sliver light, XSLT views).
  2. Server API’s (LINQ).
  3. Connected Client API’s (REST, Client OM).
  4. Application Model (Sites) – External lists.
  5. Power Shell
Cheers!!!

Sunday, September 25, 2011

SharePoint 2007 upgrade to SharePoint 2010 Basics

So all set...for upgradation...still not sure....what to do and specially how to do....ok lets start in 3 phases......This is part 1 of the complete post. Let's understand the basics.

Few steps are required before even you start with upgradation like:

Learn Phase – Focus on understanding what you have today and where you plan to go tomorrow. Know about your data and sites structure.
 
Prepare Phase – Detailed planning for SharePoint 2010 upgrade.
 
Test Phase – Testing the upgrade process. Create a test server and do this exercise there and see issues coming, log them with resolution so at the time of actual upgradation if you see any similar issue so you have the solution ready with you...right!!!

Implement Phase – Perform the actual upgrade.

Validate Phase – Validate the success of the upgrade.

User Training: Apart from these phases, user training is also a required phase here as tomorrow if users are not sure where to go....mainly navigation and site permissions....these are the two areas definitely where user training is very much required. SharePoint 2010 ribbon is most amazing thing for the new users and believe me not easy to understand for a user who was working in SP 2007 environment.

In SharePoint 2010 there are two upgrade methods available.

  • In-Place Upgrade
  • Database Attach Upgrade
Note: There is no Gradual Upgrade method available for upgrading SharePoint 2007 to SharePoint 2010.

There is also no direct upgrade method from SPS 2003 to SharePoint 2010. So if you want to upgrade from SPS 2003 to SharePoint 2010 you will have to upgrade SPS 2003 to MOSS 2007 and then from MOSS 2007 to ShaePoint 2010.

Would provide more detailed information on these 2 with screenshots in next blogs...keep an eye... :)

Cheers!!!

Saturday, September 24, 2011

Office 2010 Web Apps and SharePoint 2010

So it work with SharePoint but what does it offer:

  1. Create, View and Edit Excel, Word and PowerPoint documents (BUT only Office 2007 and 2010 documents – docx, pptx, xlsx)
  2. View and edit Word documents
  3. Co-author Excel files (really! two people editing the same file at the same time and see each other’s changes as they are made!)
  4. View PowerPoints, with transitions, fades, etc! In the browser or as a full screen slide show.
Installation Instructions:

More about it:
http://www.youtube.com/watch?v=pr3sbVvB4HA

Cheers!!!

Inline Editing for Views | SharePoint 2010

One new piece of functionality in SharePoint 2010 is the ability to add "Inline Editing" to a list view. When selected, this option allows for user to add or edit existing list items from the view without having to open the new or edit pages. Since this is added as part of the view, it can be referenced in any web part.




Configuring this option is as easy as modifying the list view. The screen shot below is an example of the list view options that need to be configured.


Once this is configured for the view you will see some additional icons. The add item icon will be displayed in the lower left of the view and the edit icon will be displayed whenever you hover over one of the list items.


When you select to add a new item using the inline editing, a new line item is created and you can enter the list information. Notice, that users are still presented with the dropdown options and the people picker options. They are also given the option to either Save or Cancel their changes.

Similarly, when selected the edit icon for an existing item, users will be able to do an inline edit of the item. Since this is option is associated with a view, any web part on the site that is referencing this view will be able to use this functionality. Below is a screenshot of a page that is configured to include a web part that uses the inline editing options. The first screenshot is of the page with the web part, the second is of the same page when the inline editing features are being used.

Cheers!!!

PowerShell...still finding cmdlets...and find hard to understand!!!


PowerShell...still finding cmdlets...and find hard to understand!!!


Use this command to see OOB examples in PowerShell window itself.

Get-Help Get-SPSite -examples

Explanation: You want to know the example of get-spsite and what all you can do in PowerShell with complete statement... :)

This will show you that....just replace the get-spsite with your required statement..and done...

Cheers!!!

Wednesday, September 21, 2011

It's not my job...and why should i know about......SharePoint HotFix..CU, Service Pack....

Difference among SharePoint HOTFIX, CUMULATIVE UPDATE and SERVICE PACK.
  1. SharePoint  Hot fix - Fixes 1 issue at a time reported by users or found by MS
  2. SharePoint  CU - Mix of more then 1 hot fix.
  3. SharePoint  Service Pack: All CU's or Hot fixes + new features....
Cheers!!!

Programmatically create a term in term set....

While adding a term in term set, though you can have other ways as well to inform users but if you want to add a term with coding in term set, this is how we can achieve that.



public class TaxonomyItemReceiver : SPItemEventReceiver

{

public override void ItemUpdated(SPItemEventProperties properties)

{

if (properties.ListItem["Approval Status"].ToString() == "0")

{

string newTerm = properties.ListItem.Title;

TaxonomyFieldValue parentTerm = properties.ListItem["Parent term"] as TaxonomyFieldValue;


TaxonomySession session = new TaxonomySession(properties.Web.Site);

TermStore mainTermStore = session.TermStores[0];

Term foundTerm = session.GetTerm(new Guid(parentTerm.TermGuid));

Term addedTerm = foundTerm.CreateTerm(newTerm, session.TermStores[0].DefaultLanguage);

mainTermStore.CommitAll();

}

base.ItemUpdated(properties);

}

}


Cheers!!!

All that glitters is not gold....specially in your case.....Managed metadata

Managed Metadata...impressive word in SharePoint 2010....

Here are some points which need special attention if you are planning to use Managed Meta-data columns in your new development sites. Use this column type only if it's not falling any of these categories.


1) No InfoPath Support

There is no InfoPath support for Managed Metadata columns. Regardless of whether this is a InfoPath form that is hosted through Forms Services or a list form it is not supported.

2) No SharePoint Workspace Support

There is also no support for Managed Metadata columns in SharePoint workspace

3) No Support in Office 2007

This is another one that gets many organizations. You can not edit Managed Metadata columns from the Office 2007 client, or 2003 for that matter. If you want to be able to edit Managed Metadata columns you need to have Office 2010 installed.

4) Cannot Edit Managed Metadata values in Datasheet Mode

You cannot edit Managed Metadata columns in datasheet mode, the selected cells are read only. Therefore for bulk changes you need to either go through each item one by one

5) Limitations in Views

There are also some limitations in the operators that you can use for views with Managed Metadata fields. You cannot use the ‘Begins With’ or ‘Contains’ operators for filters in views.

6 ) Cannot be used in calculated fields

You cannot use a Managed Metadata Column for calculated fields. So if you have a requirement to do a calculated field you will need to use another column type

7) Maximum of 250 terms selected per Managed Metadata Column

you can only have a maximum of 250 terms selected for a particular column otherwise you get an error.

8) Cannot add a Managed Metadata Column through SharePoint Designer

Although you can add a Managed Metadata column via the web interface you cannot add a Managed Metadata column with SharePoint Designer 2010.

Tuesday, September 20, 2011

Please Take Care : Managed Metadata Column Limitations

Here are some points which need special attention if you are planning to use Managed Meta-data columns in your new development sites. Use this column type only if it's not falling any of these categories.

1) No InfoPath Support


There is no InfoPath support for Managed Metadata columns. Regardless of whether this is a InfoPath form that is hosted through Forms Services or a list form it is not supported.

2) No SharePoint Workspace Support

There is also no support for Managed Metadata columns in SharePoint workspace

3) No Support in Office 2007

This is another one that gets many organizations. You can not edit Managed Metadata columns from the Office 2007 client, or 2003 for that matter. If you want to be able to edit Managed Metadata columns you need to have Office 2010 installed.

4) Cannot Edit Managed Metadata values in Datasheet Mode

You cannot edit Managed Metadata columns in datasheet mode, the selected cells are read only. Therefore for bulk changes you need to either go through each item one by one

5) Limitations in Views

There are also some limitations in the operators that you can use for views with Managed Metadata fields. You cannot use the ‘Begins With’ or ‘Contains’ operators for filters in views.

6 ) Cannot be used in calculated fields

You cannot use a Managed Metadata Column for calculated fields. So if you have a requirement to do a calculated field you will need to use another column type

7) Maximum of 250 terms selected per Managed Metadata Column

you can only have a maximum of 250 terms selected for a particular column otherwise you get an error.

8) Cannot add a Managed Metadata Column through SharePoint Designer

Although you can add a Managed Metadata column via the web interface you cannot add a Managed Metadata column with SharePoint Designer 2010.


Cheers!!!

Block SharePoint installations

If you want to block users from installing SharePoint Server 2010 and related products on Server. Try this registry setting on machine.
HKLM\Software\Policies\Microsoft\Shared Tools\Web Server Extensions\14.0\ SharePoint\DWORD DisableInstall


To block installations, set DWORD DisableInstall=00000001

When this registry key is set, users who try to install SharePoint Server 2010 receive the following error message:


SharePoint installation is blocked in your organization. Please contact your network administrator for more details.

Cheers!!!

Monday, September 19, 2011

Loopback check: Cannot access SharePoint from the SharePoint server

The solution is to modify the registry to disable the Loopback check as per Microsoft knowledge base article KB896861.

The loopback check security feature is designed to help prevent reflection attacks on a computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name. Basically this is by design and you will need apply this "fix" if you want to access SharePoint from the server.
The knowledge base article has two methods in it to address the issue, I personally use Method 2 when related to SharePoint.
My steps are:
  1. Click Start, click Run, type regedit, and then click OK.
  2. In Registry Editor, locate and then click the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  3. Right-click Lsa, point to New, and then click DWORD Value.
  4. Type DisableLoopbackCheck, and then press ENTER.
  5. Right-click DisableLoopbackCheck, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Quit Registry Editor, and then restart your computer.
Warning: Please be careful when editing the registry.

SharePoint 2010 : What's New and Improved

Friday, September 16, 2011

Open a SharePoint 2010 Site and see error "FILE NOT FOUND"....

The most possible cause of this issue is referred master page is having some issues and not working fine for your site. (Default.master, V4.master or any other referred master page)


Possible Issue: These master page refers 2-3 .ascx controls in the very first 2-3 lines (if you open the master page in designer) and there the either the address is wrong or the ascx controls are missing.

Immediate Fix:

1. Try to access "http://youserver/_Layouts/ChangeSiteMasterPage.aspx"

- Replace Yourserver with the actual server name. If you get the same error, try 2nd and if not, change the master page name to something else on both the places.

2. Open the site in SharePoint Designer 2010 and change the master page from the current to any other working master page and save and see if this work.

Complete Fix:

1. On the error page, correlation id, see the "X" sign, close it, you should see next corrlation id, keep closing. So you have more then 1 issue if you see multiple errors.

2. Access site again and go to 14 hive of the server and check the recent server logs and search for the word "Error". It will give you the exact issue.

2.1 . Download the ULS Viewer from http://archive.msdn.microsoft.com/ULSViewer/Release/ProjectReleases.aspx?ReleaseId=3308 and install on your server for better view of this issue.

3. If it's missing these ascx controls, fix the correct address by referring it from other master pages.

4. Reset IIS if required.




Assumption: You are the owner of the production environment, otherwise you will have to work with your admin to fix this.



Only for DEV Machine: Open the web.config of application and 1 in your 14 hive folder, set the debug mode to on and you should see the actual error on the page and not the correlation id. Not more CorrelationID's and see the actual error.....(DOT NET,C# GUYS like this.....:).. )





Thursday, September 15, 2011

SharePoint Requirement solved with JQuery

My client asked me to hide the NEW option dropdown from the library in SharePoint. One option was to use the SharePoint Designer and just remove or hide it from there.

Second i got using the JQuery :)








You can download the JQuery class from site or refer it to google address directly. Better option is to keep it in site assets or any other library and refer it from there.

Consuming External Data with Business Connectivity Services


CorrelationID..........No...i don't want to see that...on my site.....now what....

CorrelationID, i believe everyone have seen this message in day to day work with SharePoint, So what you do after that....no clue....send a mail to admin and ask him what' s the issue and fix it....believe me it's simple to see what's the real issue and fix it. Here we have few tools and options to help....


Callstack, compilation, and customErrors. These are three attributes you can change to true, @debug=true, and @mode=Off, that allow you to view an exception text right on the web page.


Developer Dashboard: The Developer Dashboard is a new addition in SharePoint 2010. It gives you a convenient way to view the details of any particular page rendering down to the database and WCF calls complete with exception traces, warnings, and time durations. You can enable Developer Dashboard by using the following command
stsadm -o setproperty -pn developer-dashboard -pv OnDemand


Event Viewer: The Event Viewer in Windows is an amazing insight into the innards of SharePoint. Some errors will surface only within the Event Viewer. Anecdotally I can tell you that many WCF errors, including those for out-of-the-box WCF services such as those for claims based authentication, seem to merrily log their errors in the Windows Event Log.


ULS Viewer: ULS is the unified logging service - which in itself has seen enhancements as compared to the SharePoint 2007 version. You can download this tool fromhttp://code.msdn.microsoft.com/ulsviewer, which lets you view ULS errors at runtime as they occur, and filter using CorrelationIDs.


CorrelationIDs: Technically this is a part of the ULS log, but not really. Classically reading ULS logs has been tough. Those multiple log files are quite wide, so you have to scroll around and sift through many such log files, line breaks, etc., to find the error trace you are looking for. Starting with SharePoint 2010, Microsoft gives you a unique ID, a GUID, for each error that occurs. This is the CorrelationID. You can use CorrelationIDs to put together the full error message as it occurred, even across multiple machines. And this can be done easily using the ULS Viewer that I mentioned above.


Fiddler: You can download Fiddler from www.fiddlertool.com. Fiddler introduces a proxy for your browser and starts to sniff all local http traffic going back and forth from your machine. It is an invaluable tool for debugging REST-based APIs and client object model calls. Starting with Internet Explorer 9, you have a network monitor built right into your browser, or you can also use Firebug, Chrome extensions, etc.


Internet Explorer extensions: Open any SharePoint page, and hit F12. This will bring up the developer extensions for Internet Explorer. Using this you can very easily run small JavaScript commands, change CSS on the fly, and change the DOM of the page entirely if you wish, or even step through JavaScript. In crafting up modern day rich client side applications, I have found this utility to be extremely valuable.


IIS 7 trace and logs: Managed code is awesome. And as more and more Microsoft products are whole heartedly adopting the managed code bandwagon, they are reaping amazing benefits from it. One such product is IIS7. With its integrated pipeline and error logging and tracing, it literally tells you what line an exception occurred at - along with a full stack trace, and http error codes. I can’t tell you how much I have found this useful in diagnosing really hard to discover HTTP 401s (HTTP Unauthorized), especially when diagnosing search, reporting services, etc. Security is a good thing, but it can also be a real pain sometimes.




Cheers!!!!

Wednesday, September 14, 2011

SharePoint 2010 and Taxonomy API’s



Term Store, Term Sets and Terms....are good but what if i want to use them in place of list columns (Creation of a complete list for a single column value like Countries name and use this list as a reference as lookup column, in InfoPath column as source...and many more....). How i will get the term store on some places where i can refer a list simply by using a web service or rest service...


How you can utilize the SharePoint API to programmatically work with Taxonomies and create terms and fetch the terms in your term store. This should give you some nice ideas on how to get going!


1. Dll Reference:


Microsoft.SharePoint.Taxonomy


You’ll find this reference here:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI\Microsoft.SharePoint.Taxonomy.dll



2. Namespaces:

So, the first thing we would like to do is to learn how we can read the taxonomies we’ve got in our store. To do this, we utilize Microsoft.SharePoint.Taxonomy.
There’s a few good-to-know classes in this namespace that we’re going to work with:
The above classes are stated in their hierarchically correct order, meaning means that you start out with the TaxonomySession which contains the TermStore, which contains the Groups.. and so on.


Reading the Metadata store (Managed Metadata Service):


Now lets generate the XML tree with it.


protected  void  Page_Load(object  sender, EventArgs  e)
{
SPSite  thisSite = SPContext .Current.Site;
TaxonomySession  session = new  TaxonomySession (thisSite);

TreeNode  treeNode = new  TreeNode ();
treeNode.Text = "Corporate MetaData" ;
tvMetadataTree.Nodes.Add(treeNode);

foreach (TermStore  termStore in  session.TermStores)
{
var  tsNode = new  TreeNode (termStore.Name, null , null , "" , null );
treeNode.ChildNodes.Add(tsNode);
//treeNode = tsNode; 

foreach (Group  group in  termStore.Groups)
{
var  node = new  TreeNode (group.Name, null , null , "" , null );
treeNode.ChildNodes.Add(node);
//treeNode = node; 
foreach (TermSet  termSet in  group.TermSets)
{
node = new  TreeNode (termSet.Name, null , null , "" , null );
treeNode.ChildNodes.Add(node);
treeNode = node;

foreach (Term  term in  termSet.Terms)
{
AddTermSet(term, treeNode);
}
}
}
}
}

void  AddTermSet(Term  term, TreeNode  treeNode)
{
var  node = new  TreeNode (term.Name, null , null , "" , null );
treeNode.ChildNodes.Add(node);
treeNode = node;

foreach  (Term  t in  term.Terms)
{
AddTermSet(t, treeNode);
}
}



The end result will be a simple TreeView control filled with the Metadata structure from the store, looking something like this:

Thursday, September 8, 2011

By Code delete All Old Versions from SharePoint 2010 Document Libraries

How many versions of a typical document do you need to keep? 5? 10? 100?

SharePoint content databases often get cluttered with redundant versions of the same documents. In some cases, I've seen presentation libraries with less than 10 GB of active content, but hundreds of GBs of content due to gradual changes.

If you're ready to clear out old versions, SharePoint 2010's Management Shell makes it easy. The script below will iterate through all lists and update them to keep only the last 2 copies. It will also loop through and delete unneeded versions.

Get-SPWebApplication
Get-SPSite -Limit All
Get-SPWeb -Limit All
ForEach-Object {ForEach($list in $_.Lists){If($list.EnableVersioning -eq $true){$list.MajorVersionLimit = 2; $list.Update(); ForEach($item in$list.Items){$item.URL; $item.SystemUpdate()}}}}

You can see that it...

  • Loops through all web applications
  • Loops through their site collections
  • Loops through their webs
  • Loops through their lists
  • If versioning's enabled, it sets the major version limit to 2

In order to remove old versions, it needs to loop through each item and perform a system update

The script can be easily amended to deal with only specific site collections / libraries. To keep a different number of versions, modify the MajorVersionLimit variable above.


Cheers!!!

Wednesday, September 7, 2011

Site and Sub-Site GUID's with STSADM

The following command displays the GUID's of all the Site Collections, root site and all it's sub-site on command prompt using stsadm utility. Same can also be achieved using PowerShell.

Displays the IDs and site map status for all site collections and subsites in the content database.
stsadm -o enumallwebs -databasename
 
Note: Replace with actual content database name. Go to Central admin > content database for the particular web application.
 
Cheers!!!

Document Sets in Sharepoint 2010 – Limitations


To resolve the list threshold issue for a list holding more then 23000 items, i was in process of using the Document Sets for the entire library and categorized by the content types.

I got to know few limitations with Document sets as i was also planning the Record Management Capabilities for these records as well.

Here we go....

- Document Sets are only available in SharePoint 2010 Server and are not part of the SharePoint Foundation 2010. This also means that the programing object model (SPFolder) is part of the SharePoint 2010 Server API and not available in the Foundation OM.

- You cannot create a Folder within a Document Set. Beware that the UI will not prevent you from doing this, but folders are not supported and likely will not work as you think they should.

- You cannot create metadata navigation in a Document Set.

- Since Document Set is being treated as a Folder, which is treated as such when you deal with operations like Record Management and File Upload. It’s a little bit inconsistent from the document-centric point of view.

- You cannot send a Document Set larger than 50MB using the Send To command.

- In general, beware when you create and use very large Document Sets (thousands of items), as the limitation and performance factor of viewing and displaying the list will be a factor.


- Download the entire document set. This is a very useful feature that did not make it into this release of SharePoint 2010. If you select the entire document set, you will notice that the “Download a Copy” button is grayed out. Fortunately, there are instructions available to add a custom button in the ribbon to add this feature.

Cheers!!!!!!!!!!!!

Monday, September 5, 2011

My Experience with SharePoint 2010 New Features


My experience with SharePoint 2010 and My Experience with Truth  by GandhiJi :)

I’ve summarized my personal favorite features in SharePoint 2010.

1) Sites (Web Experience)

Microsoft have incorporated the Office Ribbon within SharePoint 2010. Not only does this allow, web editing ‘in place’ ( WYSIWYG, ‘Drag and Drop’ etc - Like many other site builders have allowed for years!), but provide support for multiple browsers.

Workspace (previously called Groove) allows offline working and synchronization. It also supports advanced features like bringing external business data offline. Its also smart enough to sync changes and not entire files!

Office Web Apps (Word, Excel, PowerPoint, OneNote etc) now means that not only can multiple people work on the same document.(Different people can work on different sections at the same time) Plus, you no longer have to have the latest version of Office stored locally on your laptop or PC. Its all done through the browser.

SharePoint Workspace Mobile Client provides a clean way to view SharePoint on mobile devices and also allows offline access. This Allows search and navigation on content within a browser

2) Communities (Enhanced Social Networking)

In true Web 2.0 fashion, Collaborative Content of Blogs, Wikis, Calendars, Discussions, Tasks, Contacts, Pictures, Video and Presence.

Social Feedback allows users to provide, Bookmarks, tagging and Ratings on ALL content types. Social Tagging allows all users to add tags to all forms of content.

User Profiles can now reflects expertise via Tagging or even make recommendations based on an Outlook or OCS plug-in that crawls your outbox and picks up the subject matters you most talk about. (This is ‘opt-in ‘of course, so your boss won’t automatically know you are an expert on Fly Fishing due to your outbound emails)

MySites contain enhanced Newsfeed (like the Status update on face book), personalized content and Quick Access to Content and social network. This also encompasses a facebook type ‘wall’ for letting users interact with each other the way they do in their personal lives.

People Connections show online presence and also allow you to search colleagues using an Interactive Organization Browser (using Silverlight)

3) Content

One of the most exciting features that I feel the business will really appreciate is Top down Taxonomy / Bottoms Up Social Tagging. Essentially, this lets Users (rather than the publisher) define what the content is (So someone might tag this blog post as “SharePoint 2010”, even though the title is completely different.) This means that content should be easier to find as the users are the ones labeling it.

Large Lists and Libraries now allow tens of Millions of documents to be stored (Big failing in MOSS 2007 was it struggled at 2,000+). Enterprise Metadata generally means it’s easier to apply Metadata (tags, keywords) and thus easier to find information.

Digital Asset Management now allows Thumbnails, Metadata and ratings for images & Video Streaming from SharePoint.

Governance & Records Management Features now make it a lot easier for compliance people to do their job using SharePoint.

4) Search

For me, this is the best and most useful component of SharePoint.

SharePoint 2010 now provides a completely Interactive Search Experience. Some much needed things like automatic search query completion (like Google or Bing), Spell Checking and Wild Cards (“Did you mean?”) generally make it easier to find stuff!. Another massive factor is generally Connectivity is a lot better.

Business Connectivity Services (BCS) replaces the Business Data Catalogue and makes it easier to both search external databases, but also provides the ability to ‘read and write’. The great thing about this also is you can create Search Connectors without writing any code using SharePoint Designer. (Free tool that comes with within SharePoint).

For Enterprise customers, FAST can be utilized (which is the mother of all search!). This will allow users to search EVERYTHING! Including multiple platforms, databases and other external systems used across the organization.

There is a lot more relevance in the search results now, as this includes social data such as tagging and usage. People Search incorporates Social Networking algorithms, so results are displayed dependent on the degrees of separation between you and your searches. (Think LinkedIn style!) A Phonetic Search Algorithm for finding names is pretty cool also.

Increased Scale and Platform Flexibility now also makes it quicker and easier to search Millions of items.

4) Insights (was B.I)

Insights will be much loved by the accounting types and generally anyone that is swamped by reporting numbers who needs to publish the data in an elegant, professional presentation style. Excel Services allows user rich visualizations such asHeat Maps and Spark lines present data. Think of a map that Police Forces could use that plots where Anti-Social behavior is happening based on an Excel Spreadsheet and you get the drift.

Performance Point Services now gives enhanced scorecards, dashboards KPI’s & navigation features. SQL Server services such as Analysis Services and Reporting Services are now easier access for reporting.

Gemini is the name for the memory database that allows reporting on Excel Spreadsheets containing millions of lines of data without needing a developer.

Visio Services – Allows rich user rich diagrams to be produced within SharePoint and also includes SharePoint workflow designer. Very handy for process mapping!

5) Composites (Custom Solutions for SharePoint)

As I said, Microsoft are really empowering the Power users and composites is a handy toolkit that gives competent users the tools they need to build their own applications without IT. These are the main ones.

SharePoint Designer

• Office Ribbon

• User Customization

InfoPath Forms Service

• Easy way to build forms

Access Services

• Lets you create and publish database applications

Sandbox Solutions

• Allows custom code to be produced in local sites without affecting the whole SharePoint Platform E.G Webparts, Event Receivers. Same will apply for “SharePoint Online”.

Business Connectivity Services (was BDC)

• 2 Way Connectivity


Cheers!!!!