So I tried to use LINQ to query the SharePoint Items. It works perfectly well for me. Here I provided my code to get the SharePoint Unique ListItems based on latest Items.

In the following example, I am first sorting the Items based on Modified field and then getting the unique item based on Title field by grouping.


using (SPSite site = new SPSite("http://localhost"))
{
using (SPWeb web = site.OpenWeb())
{
SPList list = web.Lists.TryGetList("MyList");
string Modi = "Modified";
List lstitems =
(from l in list.Items.OfType<SPListItem>() orderby l[Modi] descending select l).ToList<SPListItem>();

var listitemDistinct = lstitems.GroupBy(item1 => item1.Title, (key, group) => group.First()).ToList();

foreach (SPListItem i in listitemDistinct)
{
Console.WriteLine("Title: " +i.Title +"Modified: " + i[Modi].ToString());
}
}
}


If the ListItems has the following items,

Result:
Title: Sample 2 Modified: 11/19/2011
Title: Sample 1 Modified: 11/18/2011

• Storage,
• Discussion Storage,
• Bandwidth,
• Hits,
• Visits

The SPSite.Usage property gives us the information of site usage, bandwidth, visits.
Here I am adding the snippet for getting the Free Space available against Storage Quota and Space used by Site Collection,

using (SPSite site = new SPSite("http://localhost"))
{
SPSite.UsageInfo susg = site.Usage;
long spaceused = (((susg.Storage + 0x80000L) / 0x100000L));
if (site.Quota.StorageMaximumLevel == 0L)
{
Console.WriteLine("Storage Quota: Not applicable");
Console.WriteLine("Free Space Available: Unlimited");
}
else
{
long sitequota = (site.Quota.StorageMaximumLevel / 0x100000L);
long freespace = sitequota - spaceused;
Console.WriteLine("Storage Quota: " + sitequota.ToString());
Console.WriteLine("Free Space Available: " + freespace.ToString() + " MB");
}
Console.WriteLine("Storage Used: " + spaceused + " MB");
}

URL: http://clearspitems.codeplex.com/

The project is in alpha stage, i have planned for adding more functionality to this tool. And I will also publish this in the format of stsadm, powershell and in Ribbon mode.

I am expecting those things to be happen within next week..

So stay tuned … :)

1. If you create an item using System Account, the workflow will not funtion properly or that couldn’t start.
2. The workflow start option was not enabled to “Start workflow automatically when an item was created”. Ensure this option was checked.
3. If you create and publish a workflow without enabling the Start option(Start workflow automatically when an item was created). And after some time you came and enable that start option & saves without Publishing also cause a problem.
4. Or remove the “Allow this workflow to be manually started” start option and Initiation workflow. Enable “Start workflow automatically when an item was created” option and Publish the workflow.

check the following link has the soltuoions for SharePoint Designer workflows, http://office.microsoft.com/en-us/sharepoint-designer-help/troubleshoot-workflow-errors-HA010237912.aspx#BM2
If the above solutions couldn’t solve the problem, the you have to create new workflow.

New Form, Edit Form and Display Form.

For some times or in some requirements, we need to hide some of the fields in List Forms. By OOB there is no page or option for hiding fields on separate form, but we can hide the fields in all forms in List.

I am just giving snippet to hide the Fields in each separate form, separately,

using (SPSite site = new SPSite(“http://localhost”))
            {
                using (SPWeb web = site.OpenWeb())
                {                   
                    SPList list = web.Lists.TryGetList(“Custom”);
                    SPField field = list.Fields.GetFieldByInternalName(“field1″);
                    //To hide the field from New Form
                    field.ShowInNewForm = false; 
                    //To hide the field from Edit Form
                    field.ShowInEditForm = false; 
                    //To hide the field from Display Form
                    field.ShowInDisplayForm = false; 
                    field.Update();
                }
            }

We can also show / hide the fields based on content Types. For Content Types, we can retrieve the field from Content Type.

SPField field = list.ContentTypes[“ctype1”].Fields.GetFieldByInternalName(“field1″);

and the add the further lines to hide the field in SharePoint Lists.

For revert back, we can set the ShowInNewForm  property as true.

I have Search Center Site, there i have Refinement panel web part in results page. To enable the modifications for Refinement Panel web part,

1)  Navigate to the Search results page through browser.

2) Edit the page by navigating Site Actions -> Edit Page

3) Select the Refinement Panel Web part, Click the edit arrow and then Click the Edit Web part menu. This opens the Web part Properties tool pane.

4) In the Refinement section, clear the Use Default Configuration check box.

5) Then modify Data view properties and other properties to view modified Refinement Panel

One of that happens on June 5th in the form of my marriage which was a beautiful moment in my life, after a 4 long year struggle with my love. Next one was I got the invitation to speak for Online SharePoint Saturday India on June 25th , and i have presented on “SharePoint 2010 Upgrade Approaches” for IT Professional Channel.

This SharePoint Saturday event experience gives me a encouragement to involve in more community activities. Enjoying my life and look forward to step up in my carrier.

SPListItem.Update() used to update all the values in SharePoint List Item including pre-defined hidden fields. If we modified the item, that will affects the Modified Date, Modified By, Version information fields.

SPList olist = oweb.Lists.TryGetList(“ListName”);
SPListItem olistitem = olist.Items[1];
olistitem.Title = “Sample List Item”
olistitem.Update();
olist.Update();

SPListItem.SystemUpdate() method used to update the values of the listitem without modifying the Modified Date, Modified By and Version information fields.

SPList olist = oweb.Lists.TryGetList(“ListName”);
SPListItem olistitem = olist.Items[1];
olistitem.Title = “Sample List Item”
olistitem.SystemUpdate();
olist.Update();

Content Scheduling was avaialble only the following conditions are true,

1. Content Approval was Enabled on Versioning Settings

2. Create major and minor (draft) versions was set to Document Version History option.

• .Net Managed Application
• Silverlight Application
• ECMA Script

These API’s are much easier to use than already exsiting WebServices.
The recomended Client API was .Net Managed Application than WebServices.