Welcome to ShanthaKumar's Blog, SharePoint and more... » List

Catch the Unique Items from SharePoint List

Shantha Kumar — Wed, 30 Nov 2011 07:27:22 +0000

I have lot of items from SharePoint List, but most of the items are duplicated. Here, I am going to give you a tips on getting unique rows from the List. For that, I googled for some time and then I found out there is no way to get the items based on CAML.

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() orderby l[Modi] descending select l).ToList();

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,

ID	Title	Modified
1	Sample 1	11/16/2011
2	Sample 2	11/17/2011
3	Sample 1	11/18/2011
4	Sample 2	11/19/2011

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

Updating SharePoint ListItems

Shantha Kumar — Sun, 06 Mar 2011 03:08:23 +0000

There are two methods available to update the List Items on SPListItem Object.
SPListItem.Update();
SPListItem.SystemUpdate();

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();

SharePoint Daily Alerts – 3

Shantha Kumar — Mon, 03 Jan 2011 17:54:21 +0000

If the user want to choose cascade or Restrict option for the lookup field, that user must have the ManageLists permission for the Lookup List.
To View the list of Permissions, check the SPBasePermissions enumeration.

How to get InternalName in ListEdit Page

Shantha Kumar — Fri, 25 Sep 2009 01:09:08 +0000

In SharePoint the column or field has two names. One is DisplayName, used to view the field name publically in all pages and another is InternalName used internally to refer the Field. This Internal name will be used in CAML Queries, during retreiving inserting and updating the list item.We can’t see this Internal name in any pages normally, but we can do some work around for getting this internalnames, such as writing the code & look in to the url of the particular field.

Now i giving a simple tip on displaying the InternalName on ListEdit page itself, this will help us in knowing internal name quickly and consume the time when we work up on List and ListItems.

For that, we have to edit the ListEdit.aspx page, which is available under :Program FilesCommon FilesMicrosoft Sharedweb server extensions12TEMPLATELAYOUTS
Before going to edit that page, backup that file and open it. This is the screenshot, taken before editing the page,
In the ListEdit page, add the Column as InternalName under Columns section,To add the header for Internalname under Columns section, Search for the following line
for (Int32 iIndex = 0; iIndex < spFields.Count; iIndex ++ )
At first we have to add the header column, for that before the above searched line there is tag with three header tags, add the following within the tag,Internal NameAfter adding the line, the code look like this,

” EncodeMethod=’HtmlEncode’/>

” EncodeMethod=’HtmlEncode’/>

<% if (!spList.ContentTypesEnabled) { %>
” EncodeMethod=’HtmlEncode’/>
<% } else { %>
” EncodeMethod=’HtmlEncode’/>
<% } %>

Internal Name

for (Int32 iIndex = 0; iIndex < spFields.Count; iIndex ++ )
And then we have to add the InternalName for each field type, for that
Search for the following if condition line,

if (spField.ReadOnlyField && !bCountRelated)

The above line checks the current field is read only or not, by default the read only fields are User and Calculated Columns
If you look in to the page, you can able to see the switch case statement under the if condition. Switch case statement checks the each read-only field type and adding the row contents such as (Display name, field type and Require or not) columns based on the field type,so we have to add the following line (column) within each case statement,
<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>

In this page, spField.InternalName displays the Internal Name for the current field type.

The above TD tag content ensures that, the each field row has its own Internalname
The else condition refers to the non-read only fields, If we add this line <%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>, the internal Name will be appeared on all the non-read only field types.

After adding all the lines, the code for the if and else condition will be look like this,

if (spField.ReadOnlyField && !bCountRelated)
{
switch (spField.Type)
{
case SPFieldType.Calculated:
rowClass = (rowClass == “”)? “ms-alternating” : “”;
%>

” HREF=”FldEdit.aspx?List=<%SPHttpUtility.UrlKeyValueEncode(spList.ID.ToString(“B”).ToUpper(), Response.Output);%>&Field=<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>”> <%SPHttpUtility.HtmlEncode(spField.Title,Response.Output);%>

” EncodeMethod=’HtmlEncode’/>

<%SPHttpUtility.HtmlEncode(GetUsedIn(spField), Response.Output);%>

<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>

<%
break;
case SPFieldType.User:
rowClass = (rowClass == “”)? “ms-alternating” : “”;
%>

” HREF=”FldEditEx.aspx?List=<%SPHttpUtility.UrlKeyValueEncode(spList.ID.ToString(“B”).ToUpper(), Response.Output);%>&Field=<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>” > <%SPHttpUtility.HtmlEncode(spField.Title,Response.Output);%>

<%SPHttpUtility.HtmlEncode(spField.TypeDisplayName, Response.Output);%>

<%SPHttpUtility.HtmlEncode(GetUsedIn(spField), Response.Output);%>

<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>

<%
break;
default:
if (spField.XPath != null && !spField.Hidden)
{
%>

<%SPHttpUtility.HtmlEncode(spField.Title,Response.Output);%>

<%SPHttpUtility.HtmlEncode(spField.TypeDisplayName, Response.Output);%>

<% if ( !spList.ContentTypesEnabled && spField.Required == true ) { %> <% ; } %>
<%SPHttpUtility.HtmlEncode(GetUsedIn(spField), Response.Output);%>

<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>

<%
}
break;
}
}
else
{
rowClass = (rowClass == “”)? “ms-alternating” : “”;
%>

<%if (Enum.IsDefined(typeof(SPFieldType), spField.TypeAsString) && spField.Type != SPFieldType.Lookup && spField.Type != SPFieldType.User) {%>
” HREF=”FldEdit.aspx?List=<%SPHttpUtility.UrlKeyValueEncode(spList.ID.ToString(“B”).ToUpper(), Response.Output);%>&Field=<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>”> <%SPHttpUtility.HtmlEncode(spField.Title,Response.Output);%>
<%} else {%>
” HREF=”FldEditEx.aspx?List=<%SPHttpUtility.UrlKeyValueEncode(spList.ID.ToString(“B”).ToUpper(), Response.Output);%>&Field=<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>”> <%SPHttpUtility.HtmlEncode(spField.Title,Response.Output);%>
<%}%>

<%SPHttpUtility.HtmlEncode(spField.TypeDisplayName, Response.Output);%>
colspan=2
class=ms-vb2>
<% if ( !spList.ContentTypesEnabled && spField.Required == true ) { %> <% ; } %>
<%SPHttpUtility.HtmlEncode(GetUsedIn(spField), Response.Output);%>

<%SPHttpUtility.UrlKeyValueEncode(spField.InternalName, Response.Output);%>

<%
}

The final outcome will be as follows,

To download the listedit.aspx page, click here!

Uploading File from Local Machine to SharePoint ListItem as an attachment

Shantha Kumar — Mon, 31 Mar 2008 05:04:19 +0000

To attach the file from Local Machine to SharePoint ListItem as an attachment, Import the System.IO namespace to use the Stream Class to read the file contents.

Use System.Web.UI.WebControls.FileUpload control is named as fileUpload in code.

Sample code for uploading the file from Local Machine to ListItem attachments as follows,

//Check the FileUpload control has the file

if (fileUpload.PostedFile != null)

{item = list.Items.Add();

item["Title"] = fileUpload.FileName;

//Read the Contents from the file in Local machine

Stream fs = fileUpload.PostedFile.InputStream;

byte[] fileContents = new byte[fs.Length];

fs.Read(fileContents, 0, (int)fs.Length);

fs.Close();

// Add the file to the ListItem as an Attachment

SPAttachmentCollection attachments = item.Attachments;

string fileName = Path.GetFileName(fileUpload.PostedFile.FileName);

attachments.Add(fileName, fileContents);

item.Update();

}