SharePoint Shared

Trigger event when field value changed in Infopath Repeating table programmatically

2012-02-16T02:39:00.000-08:00

Requirement: To update a field value in a repeating table when another field value is changed.

Solution: In the Infopath form, select the field that you want to apply event, go to Tools menu, select Programming > select Changed Event

This will redirect you to the VSTO event, write the code to change the main data source.

Backup your Site Collection in Sharepoint

2012-02-15T10:00:00.000-08:00

Here is a good link to create scheduler task to backup SharePoint site collection http://www.sharepointfix.com/2008/11/back-up-and-restore-your-site.html

'NaN' in InfoPath Decimal/ percentage field

2012-01-26T09:23:00.000-08:00

In InfoPath 2007, we used to get NaN in our calculated decimal fields. So, I tried to add a Rule to check if the value is NaN and replace it is with '0' if it is true. However, there is no option to check if the value of a decimal field with a text NaN

So the workaround for this is, change the field type to text and add the rule as below. After creating the rule, again change the field type to Decimal.

Sumproduct in InfoPath 2007

2012-01-25T08:40:00.000-08:00

An workaround to do similar to excel Sumproduct function in InfoPath 2007

We had a requirement to calculate the sum of product of 2 column in a repeating table. See the screen shot below

Sales Tax is a Decimal field with Percentage format enabled
Quantity is an integer
Purchase Price is Decimal field
Monthly Total is Decimal field

We want the Monthly Total value to be
Monthly Total = Sum(Quality * Purchase Price) * percentage of Sales Tax

Since there is no option to do the sum(Quality * Purchase) in InfoPath as SUM XPath function takes only a node set as parameter, I've created a field named QuantityPurchasePrice to have the product of Quality and Purchase Price and made the field hidden by setting the conditional formatting as below

Now apply the following formula in the Total field

sum(QuantityPurchasePrice) * (1 + SalesTax)

..and with some sample value, the output is

unbound (control cannot store data)

2012-01-23T02:14:00.000-08:00

Scenario: In Design view of a InfoPath 2007 form, had several controls within a table and the table is placed within a section control. Deleted the section control and got the following error in all the controls within the section

Issue: Error in controls as "unbound (control cannot store data)"

Reason: The controls has unbind

Resolution: Right click each control, click Change Binding and from the data source, select the appropriate field in which to store the control data .

The transaction log for database 'SharePoint_Config' is full

2011-12-27T04:28:00.000-08:00

Scenario: Tried to change web application settings from Authentication Providers page from Central Administration

Problem: Received the error "The transaction log for database 'SharePoint_Config' is full" when tried to save the updated settings.

Resolution: Found that the drive that containing the config database log is having very few space remaining.

Following steps helped to resolve this issue

1. Do full backups of all the SharePoint databases.

2. Open the database, right click SharePoint Config database > Properties

3. Select Simple under Recovery model list > Click OK

4. Right click the database, Tasks > Shrink > Files

5. In File type select Log

6. Click OK

Refer to the following post for more information

http://alstechtips.blogspot.com/2011_04_07_archive.html

Your backup is from a different version of Windows SharePoint Services and cannot be restored to a server running the current version. The backup file should be restored to a server with version '12.0.0.6535' or later.

2011-10-31T06:10:00.000-07:00

I tried to backup and restore a site collection from our production server to development. Our production is MOSS 2007 64 bit and Development is MOSS 2007 32 bit.

I got the following error when tried to restore the backed up file

"Your backup is from a different version of Windows SharePoint Services and canno t be restored to a server running the current version. The backup file should be restored to a server with version '12.0.0.6535' or later."

When I checked the version of each SharePoint site Site Actions > Site Settings, both had different versions. In order to have a successful restoration, we need to sync both the SharePoint versions.

We were having version 12.0.0.6535 in production and 12.0.0.6421 in development.

I have fixed the issue by installing KB983444 which brought the MOSS 2007 to version 12.0.0.6535.
Run the Config wizard after patch/hotfix/kb applied.

I'm able to use stsadm to restore from my backup into the new MOSS 2007 site.

Reference:
http://technet.microsoft.com/en-us/security/bulletin/MS10-039

http://www.microsoft.com/downloads/details.aspx?familyid=3841ceda-d0af-4e5e-8a1a-7dd954850783

The file '/_Layouts/Bamboo.ProjectPortfolioDashboard/HandleDataForCharts.ashx' does not exist.

2011-10-24T03:33:00.000-07:00

Issue: We have installed the Bamboo's Project Portfolio Dashboard solution in our production environment without any issues, however, when we add the Web Part, the images in the Web Part were not loaded and getting the following error

The file '/_Layouts/Bamboo.ProjectPortfolioDashboard/HandleDataForCharts.ashx' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.SimpleHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Note: Our SharePoint site is SSL enabled. The WebPart is working in http and not on Https. When contacted Bamboo we have been told that the issue is not with their setup and it is with our environment.

Resolution: We checked that the file HandleDataForCharts.ashx does exist at the _layouts folder. We finally found out that an HttpHandler entry is missing in the web.config file

We were able to resolved the issue by adding the following web.config entry under <httpHandlers> section

<add verb="*" path="*.ashx" type="Bamboo.HandleDataHelper.HandleDataForCharts" validate="false" />

The following link http://msdn.microsoft.com/en-us/library/bb515343.aspx helped us to resolve the issue

Multi-level Approval Workflow in Visual Studio

2011-09-30T03:30:00.000-07:00

Requirement: We have a requirement to create a Multi-level approval workflow for document libraries. I need to use SharePoint groups for each level of approval/review as there are multiple users need to review the document and approve and don't want to hard code the SharePoint groups. Can we create a custom workflow section where I can set the 'level of approvals' and 'Approvers' for each level when assigning a workflow for a document library

Solution: Create a workflow association page using VS.NET 2008. Refer to my previous post for more info.

Attached the screen shots of final output
Page 1:

Page 2:

The codebehind page of the association page (aspx page) will have the code to create SharePoint groups for "Reviewers"(1st level approval) and "Approvers"(2nd level approval) on submit. All the workflow related activities is handled in the Workflow coding.

Trigger event when workflow is added to a document library

2011-09-30T03:22:00.000-07:00

Requirement: I've created a custom sequential workflow using Visual studio and wanted to create SharePoint group when the workflow is added to a document library.

Issue: There is no event or activity associated to the Workflow which will be triggered when we add a Workflow to a document library of list. Also there is no event associated with document library or list that to be triggered when a workflow is added to it.

Solution: Create an association and initiation form in a workflow using VS.NET 2008. You can use either .aspx or InfoPath forms in a workflow. Association and initiation forms are displayed for users to complete before any workflow actually starts.Association forms are displayed to administrators when they first decide to add or associate a workflow with a particular list, document library, or content type. You can use association forms to let an administrator specify parameters, default values, and other information for the workflow as it applies to items on the list, library, or content type with which the administrator is associating it.

Below are some excellent resource I referred to and implemented successfully. Please refer to
http://msdn.microsoft.com/en-us/library/cc297199(v=office.12).aspx

Workflows for WSS3 Demystifying ASPX forms association

http://sergeluca.wordpress.com/2008/11/20/step-by-step-tutorial-creating-workflows-with-windows-sharepoint-services-and-moss-2007-part-1420-easy-aspx-association-forms-my-small-generic-framework/

Insert a Sharepoint list item from web services

2011-08-28T23:43:00.000-07:00

The following code is used to insert an item to a list using SharePoint Web Services.

/// <summary>
/// Method to insert picture URL to a list
/// </summary>
/// <param name="pictureURL">URL of the picture</param>
/// <param name="currentlLoginID">Current logged in user</param>
private void InsertItem(string pictureURL,string currentlLoginID)
{

/*Declare and initialize a variable for the Lists Web service.*/
spsService.Lists listService = new spsService.Lists();

/*Authenticate the current user by passing their default
credentials to the Web service from the system credential cache.*/
listService.Credentials = System.Net.CredentialCache.DefaultCredentials;

listService.Url = "http://spsService/sites/MP/_vti_bin/Lists.asmx";

System.Xml.XmlNode ndListView = listService.GetListAndView("Team Profiles", "");
string listName = ndListView.ChildNodes[0].Attributes["Name"].Value;
string viewName = ndListView.ChildNodes[1].Attributes["Name"].Value;

XmlDocument xmlDoc = new XmlDocument();

/* Declare an XmlNode object and initialize it with the XML response from the GetListItems method.*/
System.Xml.XmlNode nodeListItems = listService.GetList(listName);

string sBatch = string.Empty;
string uid = "-1;#" + currentlLoginID;

//Query to insert data
sBatch = "<Method ID=\"1\" Cmd=\"New\">";
sBatch += "<Field Name=\"ID\">New</Field>";
sBatch += "<Field Name=\"User_Picture\">" + pictureURL + "</Field>";
sBatch += "<Field Name=\"UID\" >" + uid + "</Field>";
sBatch += "</Method>";

XmlElement batch_element = xmlDoc.CreateElement("Batch");
batch_element.SetAttribute("OnError", "Continue");
batch_element.SetAttribute("ViewName", viewName);

batch_element.InnerXml = sBatch;
listService.UpdateListItems(listName, batch_element);
}

List all SharePoint Databases

2011-08-17T05:53:00.000-07:00

Before migrating/moving the SharePoint database, we need to find all the database name.

We may need to find move the following database

Databases for Shared Services Providers (SSPs)
Search databases for SSPs
Content databases
Search database
Central Administration content database
Configuration database

To find all the SP database names, Go to Central Administration >> Operations >> Perform a Backup. This will take you to the page with all database listed.

Cannot find ContentPlaceHolder 'PlaceHolderPageTitle' in the master page '~masterurl/default.master', verify content control's ContentPlaceHolderID attribute in the content page

2011-08-15T09:39:00.000-07:00

Error: "An unexpected error has occurred" in almost all the list and document library pages in SharePoint site

Cause: Changed the master page from SharePoint designer by right clicking the master page file and selecting "Set as default master page".

Resolution: By updating the callstack=true in web.config file of the web application, we got more detailed error message

Cannot find ContentPlaceHolder 'PlaceHolderPageTitle' in the master page '~masterurl/default.master', verify content control's ContentPlaceHolderID attribute in the content page

Opened the master page in the SharePoint designer and noticed that the PlaceHolderPageTitle is missing.
So replaced the below line
<Title>Our Company Intranet</Title>
with
<Title ID=onetidTitle><asp:ContentPlaceHolder id=PlaceHolderPageTitle runat="server"/></Title>

and save the master page.

Trim the text in the multiple line of text field in a list and add a tool tip using SharePoint Designer 2007

2011-07-30T03:29:00.000-07:00

1. This is the sample list which is currently displaying full text from multiple line of text field “Remarks"

2. Open the site in SharePoint designer , navigate to the list default view page.(In this example we are using AllItems.aspx page)

3. Right click on the List View Web Part and select “Convert to XSL T Data View”. This will automatically convert settings for the current view into data view parameters.

4. After converting to XSLT, select the remarks field and switch to code view, you will see the code to display the remarks field as below

<TD Class="{$IDAWNV5H}"><div dir="{ddwrt:GetVar('Direction')}">
<xsl:value-of disable-output-escaping="yes" select="@remarks" />
</div></TD>

We need to change the above line of code as below

<TD Class="{$IDAXNQ1G}" style="height: 22px">
<div dir="{ddwrt:GetVar('Direction')}" title="{@remarks}">
<xsl:choose >
<xsl:when test="@remarks != ''" >
<xsl:value-of disable-output-escaping="yes" select='concat((substring(@remarks,1,20)),"...")' />
</xsl:when>
<xsl:otherwise>
<xsl:value-of disable-output-escaping="yes" select="@remarks" />
</xsl:otherwise>
</xsl:choose>
</div></TD>

5. Save the file. Now you will see the trimmed text in the default view page

Error: The search request was unable to connect to the Search Service

2011-07-11T05:47:00.000-07:00

Scenario: Recieved an error in our SharePoint site when we try to search contents

Error message: "The search request was unable to connect to the Search Service"

Resolution:

1. Go to Central Admin > Operations > Services on Server > Office SharePoint Server Search Service
Make sure the "Use this server for serving search queries" is checked.

2. Also verify that the search account is configured in both search services
Go to Central Admin > Operations > Services on Server > Office SharePoint Server Search service
Go to Central Admin > Operations > Services on Server > Windows SharePoint Services Search

3. Make sure the search account specified in "Default content access account" is used on above settings.

Create subsite programmatically when a new item is created in a SharePoint list

2011-07-02T03:48:00.000-07:00

Code snippet to create sub site when a new item in list. Create a feature and bind this event handler to itemadding event.

public override void ItemAdding(SPItemEventProperties properties)
{
base.ItemAdding(properties);

string sitename = string.Empty;
string newSiteURL = string.Empty;
string siteShortName = string.Empty;
string strTemplateName = "Blank Site Template";

try
{
sitename = properties.AfterProperties["Title"].ToString();
siteShortName = GetAcronym(sitename.Trim());

if (properties.ListTitle == "Projects")
{
SPWeb website = properties.OpenWeb();
website.AllowUnsafeUpdates = true;

using (SPSite site = website.Site)
{
//to check if the site name/URL already exists
SPWeb web = site.AllWebs[website.ServerRelativeUrl + "/" + siteShortName];
int i = 0;

//if site exists, loop through with appending number at the end of site URL
while (web.Exists)
{
i = i + 1;
web = site.AllWebs[website.ServerRelativeUrl + "/" + siteShortName + i];
}

if (i != 0)
{
siteShortName = siteShortName + i;
}

//Create subsite
newSiteURL = CreateSubSite(website.Url, siteShortName, sitename, strTemplateName);

//Updating the sub site URL in the list's URL field
if (!string.IsNullOrEmpty(newSiteURL))
{
properties.AfterProperties["URL"] = newSiteURL;
}
website.AllowUnsafeUpdates = false;
web.Dispose();
}
}
}
catch (Exception ex)
{
//handle exception
}
}

/// [summary]
/// Method to create subsite
/// [summary]
/// [param name="parentSiteURL"]Parent site URL [param]
/// [param name="siteURLRequested"]site name acronym to be appended in subsite URL [param]
/// [param name="siteTitle"]Site Name [param]
/// [param name="siteTemplateName"]Site Template Name [param]
/// [returns]site URL [returns]
private string CreateSubSite(string parentSiteURL, string siteURLRequested, string siteTitle, string siteTemplateName)
{
const Int32 LOCALE_ID_ENGLISH = 1033;
string newSiteURL = string.Empty;
try
{
SPSecurity.RunWithElevatedPrivileges(delegate()
{
using (SPSite siteCollection = new SPSite(parentSiteURL))
{
using (SPSite site = new SPSite(parentSiteURL))
{
using (SPWeb parentWeb = site.OpenWeb())
{
SPWebTemplateCollection Templates = parentWeb.GetAvailableWebTemplates(Convert.ToUInt32(LOCALE_ID_ENGLISH));
SPWebTemplate siteTemplate = Templates[siteTemplateName];

//create subsite
using (SPWeb newSite = parentWeb.Webs.Add(siteURLRequested, siteTitle, "", Convert.ToUInt32(LOCALE_ID_ENGLISH), siteTemplate, false, false))
{
if (!string.IsNullOrEmpty(newSite.Url))
newSiteURL = newSite.Url.ToString();
}
}
}
}
});
return newSiteURL;
}
catch (Exception ex)
{
//handle exception
}
}

/// summary>
/// Function to get the acronym of the site name
/// summary>
/// [param name="strSiteName"]Site Name [param]
/// [returns]acronym value[/returns]
private string GetAcronym(string strSiteName)
{
string shortName = string.Empty;
string[] txtArray = strSiteName.Split(' ');
try
{
//if site name is a single word, get the first three characters of the site name
if (txtArray.Length == 1)
{
return strSiteName.Substring(0, 3);
}

//Get the first letter of each word in the site name
foreach (string word in txtArray)
{
shortName += word.Substring(0, 1);
}
return shortName;
}
catch (Exception ex)
{
// handle exception
}
}

SharePoint Useful CodePlex Tools for SharePoint

2011-07-01T06:36:00.000-07:00

To manage where the column are displayed (e.g.: new or edit mode). To Hide columns from newform.aspx, editform.aspx and dispform.aspx etc
http://wsslistconfigurator.codeplex.com/

To add 'Only their own' permission for the document library.
http://moresharepoint.codeplex.com/

Ad Rotator WebPart
http://spadrotator.codeplex.com/

Caml Query Builder
http://spcamleditor.codeplex.com

JQuery SPServices
http://spservices.codeplex.com

Hit Counter WebPart
http://hitcounter.codeplex.com/

Cascading drop downs
http://customfieldcontrols.codeplex.com/
http://cascddlistwithfilter.codeplex.com/

To manage alerts on list or item for SharePoint groups.
http://advancedalert.codeplex.com/

Useful Sharepoint Designer Custom Workflow Activities
http://spdactivities.codeplex.com/wikipage?title=Copy%20List%20Item%20Extended%20Activity&ProjectName=spdactivities

SharePoint User Change Password
http://userchangepassword.codeplex.com/

List of users and their access
http://accesschecker.codeplex.com/

SharePoint Navigation Menu
http://spnavigationmenu.codeplex.com/

Filter data in a DataView Web Part using SharePoint Designer

2011-06-14T10:10:00.000-07:00

Follow the steps to filter the Overall Project Status by its Status, Assume that we need to list all the project that are in open status.

Open the page that contains the Data View that you want to filter.
Right-click the Data View, and then click Show Common Control Tasks on the shortcut menu.

In the Common Data View Tasks list, click Filter.
In the Filter Criteria dialog box, click Click here to add a new clause.
Select more fields from Field Name drop down
Select the field Status field and Click Ok
Enter the value as Open in the Value field and click OK
Save the file and refresh the page to verify the webpart.

Check if a folder exists in a SharePoint List

2011-06-02T07:38:00.000-07:00

Below code is to check if the folder already exists in a List.

private void CreateFolderInList(string folderName, string listName, SPListCollection listCollection)

{

try

{

//Creating folder in "Sites" Lists

SPList list = listCollection[listName];

//Check if the Folder is already available in the list

SPQuery query = new SPQuery();

query.Query = "<Where><And><Eq><FieldRef Name='Title'/><Value Type='Text'>" + folderName + "</Value></Eq><Eq><FieldRef Name=’FSObjType’/><Value Type=’Lookup’>1</Value></Eq></And></Where>";

query.ViewAttributes = "Scope=\"RecursiveAll\""

//Retrieve the items based on Query

SPListItemCollection items = list.GetItems(query);

//Item count is "0" if the folder does not exist

if (items.Count == 0)

{

folderItem = list.Items.Add(list.RootFolder.ServerRelativeUrl, SPFileSystemObjectType.Folder);

folderItem["Title"] = folderName;

folderItem.Update();

//return folderItem.Url;

}

catch (Exception ex)

{

}

Prevent duplicate item in a SharePoint List

2011-06-02T02:25:00.000-07:00

The following Event Handler code will prevent users from creating duplicate value in "Title" field.

ItemAdding Event Handler

public override void ItemAdding(SPItemEventProperties properties)
{
base.ItemAdding(properties);
if (properties.ListTitle.Equals("My List"))
{
try
{
using(SPSite thisSite = new SPSite(properties.WebUrl))
{
SPWeb thisWeb = thisSite.OpenWeb();
SPList list = thisWeb.Lists[properties.ListId];
SPQuery query = new SPQuery();
query.Query = @"<Where><Eq><FieldRef Name='Title' /><Value Type='Text'>" + properties.AfterProperties["Title"] + "</Value></Eq></Where>";
SPListItemCollection listItem = list.GetItems(query);
if (listItem.Count > 0)
{
properties.Cancel = true;
properties.ErrorMessage = "Item with this Name already exists. Please create a unique Name.";
}
}
}
catch (Exception ex)
{
PortalLog.LogString("Error occured in event ItemAdding(SPItemEventProperties properties)() @ AAA.BBB.PreventDuplicateItem class. Exception Message:" + ex.Message.ToString());
throw new SPException("An error occured while processing the My List Feature. Please contact your Portal Administrator");
}
}
}

Feature.xml

<?xml version="1.0" encoding="utf-8"?>
<Feature Id="1c2100ca-bad5-41f5-9707-7bf4edc08383"
Title="Prevents Duplicate Item"
Description="Prevents duplicate Name in the "My List" List"
Version="12.0.0.0"
Hidden="FALSE"
Scope="Web"
DefaultResourceFile="core"
xmlns="http://schemas.microsoft.com/sharepoint/">
<ElementManifests>
<ElementManifest Location="elements.xml"/>
</ElementManifests>
</Feature>

Element.xml

<?xml version="1.0" encoding="utf-8" ?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Receivers ListTemplateId="100">
<Receiver>
<Name>AddingEventHandler</Name>
<Type>ItemAdding</Type>
<SequenceNumber>10000</SequenceNumber>
<Assembly>AAA.BBB, Version=1.0.0.0, Culture=neutral, PublicKeyToken=8003cf0cbff32406</Assembly>
<Class>AAA.BBB.PreventDuplicateItem</Class>
<Data></Data>
<Filter></Filter>
</Receiver>
</Receivers>
</Elements>

Microsoft® Community Contributor Award

2011-05-30T22:17:00.000-07:00

Happy to brag.....

Thank You Microsoft.

Email the Approval Status to "Created By"/"Modified By" user from Visual Studio workflow

2011-05-27T04:45:00.000-07:00

Below is the code snippet to send an email about the approval status to the user who submitted/created the list item in a SharePoint list. Assume that the Visual studio workflow is attached to the list and will trigger the workflow when the item is edited in the list.

if (workflowProperties.Item.ModerationInformation.Status == SPModerationStatusType.Denied)
{
       StringDictionary headers = new StringDictionary();
        headers.Add("from", "administrator@domain.com");
        headers.Add("subject", "Request - Denied");
        headers.Add("content-type", "text/html");
        System.Text.StringBuilder strMessage = new System.Text.StringBuilder();

       //link to list item display form (view item)
       strMessage.Append("The request submitted in ABC site has been rejected."+ workflowProperties.WebUrl+ "/" + workflowProperties.List.Forms[PAGETYPE.PAGE_DISPLAYFORM].Url + "?ID=" + workflowProperties.ItemId);
        strMessage.Append("<br><br> Approver's comments: "+ workflowProperties.Item.ModerationInformation.Comment);

      SPListItem item = workflowProperties.Item;
        SPUser spUser = GetSPUser(item, "Created By");
        if (!String.IsNullOrEmpty(spUser.Email))
        {
                headers.Add("to", spUser.Email);
                SPUtility.SendEmail(web, headers, strMessage.ToString());
        }
}

//Function to get the user instance who submitted the item
private SPUser GetSPUser(SPListItem item, string fieldName)
        {
            SPFieldUser field = item.Fields[fieldName] as SPFieldUser;
            if (field != null && item[fieldName] != null)
            {
                SPFieldUserValue fieldValue = field.GetFieldValue(item[fieldName].ToString()) as SPFieldUserValue;
                if (fieldValue != null)
                {
                    return fieldValue.User;
                }
            }
            return null;
        }

Limited Access permission in SharePoint

2011-05-24T07:28:00.000-07:00

Scenario: We have a list which doesn't inherit permissions from the site. Also, at the root of the list, there are folders, which are also set to NOT inherit permissions from the parent folder (which is the root of the list). We have added a Site group to the folder with 'Contribute' permission.

Issue: We see that the site group which we added to the folder is also added automatically at list level as well. The group have “Limited Access” permissions to the list.

Explanation: When you set permissions (for example: Full Control/Contribute) to the Folder after you break the permissions inherit. The users\group will have “Limited Access” permissions to the list, not the same permissions with the folder.

In SharePoint, anonymous users’ rights are determined by the Limited Access permission level. Limited Access is a special permission level that cannot be assigned to a user or group directly. The reason it exists is because if you have a library or subsite that has broken permissions inheritance, and you give a user/group access to only that library/subsite, in order to view its contents, the user/group must have some access to the root web. Otherwise the user/group will be unable to browse the library/subsite, even though they have rights there, because there are things in the root web that are needed to render the site or library. Therefore, when you give a group permissions only to a subsite or library that is breaking permissions inheritance, SharePoint will automatically give Limited Access to that group or user on the root web.

Source:
More information about “Limited Access” permissions:
http://office.microsoft.com/en-us/windows-sharepoint-services-help/permission-levels-and-permissions-HA010100149.aspx
http://paulgalvinsoldblog.wordpress.com/2008/11/02/what-is-limited-access-anyway/

Send an email with html format using SPUtility.SendEmail

2011-05-23T07:14:00.000-07:00

SPWeb oWeb = SPContext.Current.Web

StringDictionary headers = new StringDictionary();

headers.Add("from", "system@domain.com");
headers.Add("to", spUser.Email);
headers.Add("subject", "Welcome to the SharePoint group: ABC site: ");
headers.Add("content-type", "text/html"); //This is the default type

System.Text.StringBuilder strMessage = new System.Text.StringBuilder();
strMessage.Append("<br><br><b>Login Instructions: </b><br>");
strMessage.Append("<font color='red'><UL><li>If you are a US employee ALWAYS login in using the following login format </font><br>");

SPUtility.SendEmail(web, headers,strMessage.ToString());

Programmatically set permissions to a folder in a SharePoint list

2011-05-17T08:02:00.000-07:00

This method can be used to bind permission to a folder in a SharePoint list

/// <summary>
/// Method to set the permission at folder level for the newly created site groups
/// </summary>
/// <param name="web">The current web instance</param>
/// <param name="groupName">Name of the Site group that is added to the folder</param>
/// <param name="listName">Name of the list</param>
/// <param name="folderName">Name of the folder in the list</param>
/// <param name="role">Role/permission level set to the group to access folder for the site group users</param>

private void SetRoleDefinitionBinding(SPWeb web,string groupName, string listName, string folderName, string role)
        {
            try
            {
                SPRoleAssignment roleAssignment = new SPRoleAssignment((SPPrincipal)web.SiteGroups[groupName]);
                SPList list = web.Lists[listName];
                SPQuery query = new SPQuery();
                    query.Query = "<Where><Eq><FieldRef Name='Title'/><Value Type='Text'>" + folderName + "</Value></Eq></Where>";
                //Retrieve the items based on Query
                SPListItemCollection items = list.GetItems(query);

                //Get the name and Url for the folder
                foreach (SPListItem item in items)
                {
                    SPFolder folder = web.GetFolder(item.Url);
                    folder.Item.BreakRoleInheritance(true);
                    roleAssignment.RoleDefinitionBindings.Add(web.RoleDefinitions[role]);
                    folder.Item.RoleAssignments.Add(roleAssignment);
                    web.Update();
                }

            }
            catch (Exception ex)
            {

                //Error handling
            }
        }

Creating a Folder in a SharePoint List and adding Items to it programatically

2011-05-12T10:15:00.000-07:00

The following code is to create a folder in a SharePoint list and add items to it. This code is written for a Custom Visual Studio Workflow, the workflow will be started when a new item is added to a list.

public Guid workflowId = default(System.Guid);
public SPWorkflowActivationProperties workflowProperties = new SPWorkflowActivationProperties();
SPList list = null;
SPListItem folderItem = null;

private void onWorkflowActivated1_Invoked(object sender, ExternalDataEventArgs e)
{
SPListCollection listCollection = workflowProperties.Web.Lists;

//Creating folder in "MyContacts" Lists
list = listCollection["MyContacts"];

// create a folder under the path specified
folderItem = list.Items.Add(list.RootFolder.ServerRelativeUrl, SPFileSystemObjectType.Folder);

// set the folder name and update
folderItem["Title"] = "My Folder"
folderItem.Update();

//create a listitem object to add item in the foler
SPListItem listItem = list.Items.Add(folderItem.Folder.ServerRelativeUrl, SPFileSystemObjectType.File, null);

//Set the values for other fields in the list
listItem["Contact ID"] = workflowProperties.Item["Contact ID"];
listItem["Contact Name"] = workflowProperties.Item["Contact ID"];
listItem.Update();
workflowProperties.Item.Update();
oWeb.AllowUnsafeUpdates = false;
}

Activity 'onWorkflowActivated1' validation failed: Cannot resolve Activity 'Workflow1'

2011-05-10T09:52:00.000-07:00

I got following error when I try to build custom workflow in Visual Studio 2008
"Activity 'onWorkflowActivated1' validation failed: Cannot resolve Activity 'Workflow1'"

To resolve this, do a search in your entire project and find any references to "Workflow1", if so, rename all the occurances with the modified class name.

Visual studio Workflows in SharePoint

2011-05-09T10:10:00.000-07:00

Good videos to start working on Basic Visual studio Workflows in SharePoint.

http://channel9.msdn.com/blogs/robertshelton/sharepoint-document-workflow-extracting-document-details-with-your-workflow

http://www.youtube.com/watch?v=gy3NW9pv7Qk&feature=player_embedded

"Save library as template" link is missing in SharePoint site

2011-05-06T07:33:00.000-07:00

Some of the document libraries and list, "Save library as template" link is hidden by default. If you go to "View All Site Content" and have a look at the description next to each library/list, the description that says "This system library was created by the Publishing feature.." will have the "Save library as template" link hidden.

This behaviour is by default, however we have a workaround for this. Go to the "Document Library Settings" page. You should see the URL address like this ".../listedit.aspx?List={GUID}", change the "listedit" to "savetmpl" and the URL look like this "../savetmpl.aspx?List={GUID}", now you will be able to save the library as a template.

This method is not recommended, but it works. If you have any workflow bound to the library then you may have some issues,but works fine if you just want to create a template for document settings, Columns and views.

To prevent users from creating folders in SharePoint document libraries

2011-05-05T07:21:00.000-07:00

The OOB method to remove the "New Folder" menu will prevent users only creating folder from the standard view and users are still be able to upload/create folders from explorer view. Below is the feature code used to prevent users from creating folders in document library even in explorer view.

Feature.xml

<?xml version="1.0" encoding="utf-8"?>
<Feature Id="62b28298-e3fc-4ccc-a2ea-3f92b7e9a21e"
          Title="Disable Folders"
          Description="Feature to disable creating new folders in document libraries in the site"
          Version="12.0.0.0"
          Hidden="FALSE"
          Scope="Web"
    ActivateOnDefault="FALSE"
          DefaultResourceFile="core"
          xmlns="http://schemas.microsoft.com/sharepoint/">
<ElementManifests>
    <ElementManifest Location="elements.xml"/>
</ElementManifests>
</Feature>

Elements.xml

<?xml version="1.0" encoding="utf-8" ?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Receivers ListTemplateId="101">
  <Receiver>
   <Name>AddingEventHandler</Name>
   <Type>ItemAdding</Type>
   <SequenceNumber>10000</SequenceNumber>
   <Assembly>AAAA.BBB.AllUsers, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9f4da00116c38ec5</Assembly>
   <Class>AAAA.BBB.AllUsers.DisableFoldersInLib</Class>
   <Data></Data>
   <Filter></Filter>
  </Receiver>
</Receivers>
</Elements>

Code:
public override void ItemAdding(SPItemEventProperties properties)
        {
            base.ItemAdding(properties);
            //If the new created file type is "folder" then the following conditions will be true
            if ((properties.BeforeUrl != properties.AfterUrl &&
                properties.ListItem == null &&
                properties.ListItemId == 0) ||
                properties.AfterProperties["ContentType"].ToString() == "Folder")
            {
                properties.Cancel = true;
                properties.ErrorMessage = "You are not allowed to create new Folders in this document library. Please tag the files with Metadata instead of creating folders.";
            }
        }

Parent child relationship for lists in SharePoint

2011-04-14T09:22:00.000-07:00

If you are looking for a project/child relationship for a Projects and Tasks list. You can try using the
Budgeting and Tracking Multiple Projects Template which is part of the SharePoint "Fantastic 40" Site Templates. Basically this template allows you to track all your projects and tasks. When you view the project item, you also get a Related tasks, Related issues and Related milestones data views on the same page.Any tasks, issues or milestones you add on this page will be associated with that particular project and will rollup onto a nice looking dashboard.

Refer to the following URL to download the template.
http://www.microsoft.com/downloads/en/details.aspx?FamilyId=04FDA604-BAB0-4E43-8B88-38101DFE121A&displaylang=en

Refer to the following site which is created using this template.
http://demo.sharesquared.com/PTPM/BTMP/default.aspx

In case if you want any extra customization, you can customize this site and save as a template to reuse it.

Move SharePoint Site Collection as a Subsite

2011-03-31T05:18:00.000-07:00

To move a site collection as a subsite to another site collection, we can make use of STSADM import/export command.

Following are the steps to achieve this

Assume that, we need to move the site collection http://sitecollection1/sites/asite to another site collection http://sitecollection2/sites/bsite as a subsite.

Steps

1. Export the site collection (http://sitecollection1/sites/asite) using STSADM command line tool

stsadm.exe -o export -url http://sitecollection1/sites/asite -filename c:\mybckup\sc_asite.bak –includeusersecurity –nofilecompression

2. Create a new site with Blank Site template in the other site collection (http://sitecollection2/sites/bsite). Assume the blank site name is csite

3. Import the backed up site collection in c:\mybckup\sc_asite.bak

stsadm.exe -o import -url http://sitecollection2/sites/bsite/csite -filename c:\backups\sc_asite.bak
-includeusersecurity -nofilecompression

After migration, the site collection 1 will be available under the following URL as a subsite http://sitecollection2/sites/bsite/csite

Unable to cast object of type 'XXXXXXXX' to type 'Microsoft.SharePoint.SPFeatureReceiver'

2011-03-29T03:45:00.000-07:00

I got the following error on deployment
"Unable to cast object of type XXXX.YYYYY' to type 'Microsoft.SharePoint.SPFeatureReceiver'

Resolution:
Removed the following entries ReceiverAssembly & ReceiverClass from feature.xml and the issue is resolved

ReceiverAssembly="XXXX.YYYYY' , Version=1.0.0.0, Culture=neutral, PublicKeyToken=9f4da00116c38ec5"
ReceiverClass="XXXX.YYYYY.ZZZZZ"

To provision a file in Pages document library

2011-03-25T09:32:00.000-07:00

Below is the feature file that is used to upload a file in to Pages document library on feature activation

Feature.xml

<?xml version="1.0" encoding="utf-8"?>
<Feature Id="21a53317-2fd7-4f21-b5c4-efc018b88154"
          Title="Add Site Users List Template "
          Description="Upload the 'All Site Users' list template to site collection"
          Version="12.0.0.0"
          Hidden="FALSE"
          Scope="Site"
    ActivateOnDefault="FALSE"
          DefaultResourceFile="core"
          ReceiverAssembly="xxxx.yyy.ListAllUsers, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9f4da00116c38ec5"
          ReceiverClass="xxxx.yyy.ListAllUsers.AddGetUsersList"
          xmlns="http://schemas.microsoft.com/sharepoint/">
<ElementManifests>
    <ElementManifest Location="elements.xml"/>
   <ElementFile Location="webpartpage.aspx"/>
</ElementManifests>
</Feature>

Elements.xml

<?xml version="1.0" encoding="utf-8" ?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Module Name="Pages" Path="" Url="Pages">
<File Name="webpartpage.aspx" Url="webpartpage.aspx" IgnoreIfAlreadyExists="FALSE"/>
</Module>
</Elements>

Once the feature is activated the file is uploaded to the document library, however I cannot view the file in default view but able to view in the Explorer view, currently working on that

List all users and groups from SharePoint site collection

2011-03-25T03:25:00.000-07:00

The following code is to generate a list on all site collection users, their groups and subsite details

- I've created a custom list named "All Site Users" with 5 columns as User Name, Groups, Site URL, Account Name, TagUsers

- The list template is uploaded programmatically on feature activation, The below code is a webpart code, which is added to a webpart page on solution deployment, when the webpart page is accessed, the following code will loop through the users in the site collection their groups and log the details to the custom list "All Site Users".

-'TagUsers' column can be used to create a view to list unique user names, condition for the view would be Filter by TagUsers=1

SPWeb rootweb = null;
                SPSite SPSite = null;
                try
                {
                   using (SPSite = new SPSite(SPContext.Current.Site.ID))
                    {
                        using (rootweb = SPSite.OpenWeb())
                        {
                            //Delete and create a new Portal Users List with updates
                            DeleteListIfExists(rootweb, "Portal Users List");
                            SPListTemplateCollection templateCollection = SPSite.GetCustomListTemplates(rootweb);
                            SPListTemplate template = templateCollection["Portal Users List"];
                            rootweb.AllowUnsafeUpdates = true;
                            //Create the Portal Users List using the PortalUsersList.stp template,                            rootweb.Lists.Add("Portal Users List", "List to display all the site collection users and their groups", template);
                            //Getting the URL of the list
                            SPList alluserslist = rootweb.Lists["Portal Users List"];
                            string ListURL = alluserslist.DefaultViewUrl;
                            Hashtable htUsers = new Hashtable();
                            //Loop all the Sites
                            foreach (SPWeb SPWeb in SPSite.AllWebs)
                            {
                                //Get All users in the subsite
                                SPUserCollection AllSPWebUsers = SPWeb.AllUsers;
                                //Loop each users in the Web/subsite
                                foreach (SPUser user in AllSPWebUsers)
                                {
                                    //Adding the user to the "Portal Users List" list
                                    SPListItem newItem = alluserslist.Items.Add();
                                    SPGroupCollection AllGroups = user.Groups;
                                    //AllGroups.Count is '0' when the users are directly added to the site
                                    if (AllGroups.Count == 0)
                                    {
                                        newItem["User Name"] = user.Name;
                                        newItem["Account Name"] = user.LoginName;
                                        newItem["Parent Site"] = SPWeb.Url;
                                        newItem["Group"] = "Individual User";

                                        if (!htUsers.Contains(user.LoginName))
                                        {
                                            newItem["TagUsers"] = 1;
                                            htUsers.Add(user.LoginName,user.Name);
                                        }

                                    }
                                    else
                                    {
                                        //Loop each group the user added to
                                        foreach (SPGroup group in AllGroups)
                                        {
                                            newItem["User Name"] = user.Name;
                                            newItem["Account Name"] = user.LoginName;
                                            newItem["Parent Site"] = SPWeb.Url;
                                            newItem["Group"] = group.Name;
                                            if (!htUsers.Contains(user.LoginName))
                                            {
                                                newItem["TagUsers"] = 1;
                                                htUsers.Add(user.LoginName, user.Name);
                                            }
                                        }
                                    }
                                    //Saving new item in the list
                                    newItem.Update();
                                }
                                alluserslist.Update();
                            }
                            //After WebPart process the entire users list, will be redirected to the "Portal Users List" page
                            SPUtility.Redirect(ListURL, SPRedirectFlags.Trusted, HttpContext.Current);
                        }
                    }
                }
                catch (ThreadAbortException)
                {
                    //Ignoring this as SPUtility.Redirect throws ThreadAbortException
                }
                   catch (Exception e)
                {
                 }
             }

InfoPath URL in Navigation

2011-03-09T04:51:00.000-08:00

If you need to provide a navigation menu in SharePoint page with the InfoPath Form URL, your URL will be truncated if it is length exceeds 256 characters, to shorted the URL we can use

~sitecollection in the URL instead of "http://servername/site"

The full URL after change would be similar like below

https://servername/sites/sitename/_layouts/FormServer.aspx?XsnLocation=~sitecollection/sitename/InfoPathForms/rrtemplate.xsn&SaveLocation=~sitecollection/sitename/FormLibName&Source=~sitecollection/sitename/FormLibName/Forms/AllItems.aspx&DefaultItemOpen=1

URL properties used in SharePoint designer

2011-03-02T02:26:00.000-08:00

Assume that https://server/sites/sitename/libraryname/formname.xml the value for the URL properties would be

Encoded Absolute URL: https://server/sites/sitename/libraryname/formname.xml

Server Relative URL: /sites/libraryname/formname.xml

URL Path: /sites/sitename/libraryname/formname.xml

To open the InfoPath XML file from Workflow email

2011-02-23T04:21:00.000-08:00

The xml files are based upon xsn or template files. XML is raw data and you need a template for the form's formatting and structure. You need to bind the URL like below:

https://server/sitesname/_layouts/FormServer.aspx?XmlLocation=[%LibraryName:Server Relative URL%]&source=form library path&DefaultItemOpen=1

Publish InfoPath 2007 form in MOSS 2007

2011-02-22T04:33:00.000-08:00

1. Design the form
2. Create a form library to store the source form template (xsn).
3. Create another form library to store all the submitted forms
4. Submit data to document library(step 2) on Submit option
5. Publish form to the form library (step 1)

Table border color always black in InfoPath table

2011-02-21T04:41:00.000-08:00

To change the border color of a table in InfoPath

1. Right-click the table that you want to change the color.
2. Click Borders and Shading menu.
3. In Borders Tab, select the color that you want to apply for the table border from color palette.
4. Under Presets, click the button for the borders that you want. (NOTE: you need to click the preset button every time you change the color, otherwise the border color remains unchanged)
5. Click OK

Add Label Control in InfoPath

2011-02-18T04:10:00.000-08:00

To add a dynamic label control in InfoPath 2007, we can use the Expression Box in Advanced Controls section.

For example, if you want to insert the current date as a dynamic label in the form,

1. Add Expression Box in the form
2. Insert function Date and Time --> Today
3. To change the Date format - Set the format under Result Section in General Tab of Expression Box Properties

Bind SharePoint list filtered data to Infopath dropdown

2011-02-16T05:21:00.000-08:00

To bind a SharePoint list data in to a combo box in InfoPath
By default the values of a specific field in a list is bind based on the default view set in the list.

To bind the values based on a different view, below are the steps

1. Form the URL of the list and view
https:////_vti_bin/owssvr.dll?Cmd=Display&List=<YourListID>&XMLDATA=TRUE&View=<YourViewID>

To get your list ID and View ID

List Settings --> Click on the View that you want to bind in the infopath drop down control

Your URL contains the List GUID and View GUID
https:///sites//_layouts/ViewEdit.aspx?List=%7B9B7BA6DE%2D0C1C%2D4832%2D8CC0%2DAF71EC3BAB46%7D&View=%7BF60E1186%2D394F%2D4BF3%2D96CD%2D0CC62C693D85%7D&Source=<>

2. Use the formed URL as your XML data source in InfoPath and your drop down data will be filtered as per your specific view
3. In InfoPath Data Connection Wizard, select XML document as your data source and provide the following URL as the XML data file

https:////_vti_bin/owssvr.dll?Cmd=Display&List=<YourListID>&XMLDATA=TRUE&View=<YourViewID>

4. Create a data connection and set that to the drop down list in the InfoPath. Now the drop down will list the data based on your specific view

Publishing vs Collaboration site

2011-01-03T04:32:00.000-08:00

Source: http://office.microsoft.com/en-us/sharepoint-server-help/default-site-templates-HA010174491.aspx#BM1

SharePoint Infopath

2010-07-27T01:14:00.000-07:00

InfoPath is based on industry-standard Extensible Markup Language (XML). Extensible Markup Language (XML) is a condensed form of Standard Generalized Markup Language (SGML) that enables developers to create customized tags that offer flexibility in organizing and presenting information. When you design a form, InfoPath creates a form template (.xsn) file, with an .xsn extension. When someone fills out a form in InfoPath, the data in that form is saved in XML format.

Why InfoPath?

Reusable data: The data stored in an InfoPath form doesn't have to remain locked in the form forever; it can be easily separated from the form and reformatted or reused in a variety of ways. This enables form designers to integrate form data into existing business processes.

Accurate data: As a user fills out an InfoPath form, the data they enter can be checked for data validation errors. If your form is connected to a database or Web service, users won't be able to submit data until they fix these errors. This helps you ensure that the data you collect is accurate and error-free, and that it conforms to whatever standards you specify.

Offline support: Unlike Web-based forms, InfoPath forms don't have to be filled out while a user is connected to a network. Users can fill out forms offline, and then submit them later, when they are reconnected.

Flexible controls: In addition to standard controls, such as text boxes and list boxes, InfoPath also includes a number of new controls, such as repeating tables and optional sections these types of controls let you create a flexible form that is designed to accommodate your users. For example, in an expense report form, you can use a repeating table to allow users to enter only as many expense items as necessary.

Tablet PC support: InfoPath allows you to design forms for Tablet PC users. In particular, you can include special controls, called ink picture controls, in your form. Tablet PC users can then add handwritten words or drawings inside these controls.

SharePoint in Commerce Server 2009

2010-04-22T00:14:00.000-07:00

Commerce Server 2009 offers new functionality: the Microsoft Office SharePoint Server (MOSS) 2007 integration, which includes an out-of-the-box commerce site based on SharePoint, and 31 Web parts to provide maximum customizability and ease of use.

In addition, your e-commerce sites can also use SharePoint functionality, such as searching, social networking, document lists, workflow and styling.

SharePoint tutorials

2010-04-20T22:48:00.000-07:00

SharePoint Fundamentals
http://msdn.microsoft.com/en-us/magazine/2007.01.sharepoint.aspx

MOSS 2007 Getting Started e-Book
http://go.microsoft.com/fwlink/?LinkID=91741

SharePoint How-To Tutorials Videos
http://dotnetguts.blogspot.com/2009/03/sharepoint-videos-for-beginner-step-by.html
http://blog.sharepointhosting.com/Downloads/SharePoint-Tutorials.aspx

SharePoint for Developers
http://msdn.microsoft.com/en-us/rampup/dd221355.aspx
http://msdn.microsoft.com/en-us/rampup/dd320759.aspx

Get Started Developing on SharePoint 2010

2010-04-14T22:50:00.000-07:00

http://msdn.microsoft.com/en-us/sharepoint/ee514561.aspx

http://msdn.microsoft.com/en-us/sharepoint/ee513147.aspx

SharePoint Interview Questions

2010-04-09T03:59:00.000-07:00

http://manomangaldas.blogspot.com/2008/01/moss-2007-sharepoint-interview.html

http://www.pointsharepoint.com/2008/03/sharepoint-interview-questions.html

http://www.dotnetfunda.com/interview/ShowCatQuestion.aspx?category=87

http://programmingsharepoint.blogspot.com/2008/02/sharepoint-interview-questions.html

http://www.sharepoint2007books.blogspot.com/

http://www.interviewhelper.org/categorydetail.php?Cat=33&level=1&title=Sharepoint

SharePoint Project Planning Guidelines

2010-04-08T06:01:00.000-07:00

http://technet.microsoft.com/en-us/library/cc261834.aspx

Downloadable book: Planning and architecture for Office SharePoint Server 2007

http://technet.microsoft.com/en-us/library/cc262757.aspx

Technical diagrams and other supplemental documentation

http://technet.microsoft.com/en-us/library/cc263199.aspx

upgrade WSS 2.0 to WSS 3.0

2010-04-08T04:46:00.000-07:00

Refer to these URLs

http://geekswithblogs.net/redwards/archive/2007/10/26/116365.aspx

http://technet.microsoft.com/en-us/library/cc288775.aspx

http://technet.microsoft.com/en-us/library/cc288400.aspx

Authentication samples

2010-03-30T03:24:00.000-07:00

http://technet.microsoft.com/en-us/library/cc262069.aspx

Sharepoint 2010 ! Key Improvements from MOSS

2010-03-26T06:02:00.001-07:00

http://www.slideshare.net/sashayz/cfakepathsharepoint2010?src=related_normal&rel=1146609

Custom Action menu

2010-03-26T05:58:00.000-07:00

Refer to the below URLs to create a custom action menu

http://msdn.microsoft.com/en-us/library/ms473643.aspx

http://blogs.msdn.com/bowerm/articles/175691.aspx

http://www.dotnetprodigy.com/2009/01/how-to-create-custom-action-specific-to.html

http://www.slideshare.net/gvarosky/introduction-to-developing-custom-actions-within-sharepoint

Difference between WSS 3.0 Search and MOSS Search

2009-11-26T03:26:00.000-08:00

WSS Search
Scalability:Search covers a single site collection. Only SharePoint content in the site collection can be crawled. You cannot crawl databases, mail servers, application servers, or Web sites and file shares outside of the site collection. In a deployment with more than one site collection, each site collection provides search only for content on that site collection, and there is no aggregation of search results across site collections.

Content sources: One content source is automatically created for each Web application in the site collection, and no administration details are exposed to administrators.

Search scopes: Search is automatically scoped to current context and limited to site and subsites, list or library, or folder. These search scopes appear in the search dropdown menu. If you are looking at a subsite, you cannot search over the entire site collection, but you can search over all of the subsites of the current site. Scope management is not exposed to administrators.

Crawling: Full crawls occur automatically without scheduling and without administrator control.

Error logging: Administrators can view a limited set of error message types, including:
- Authorization messages.
- Propagation messages.
- Hardware failure and data corruption messages.

IFilters: A limited set of IFilters to search content in certain formats are included with Windows SharePoint Services 3.0. Other IFilters are available by installing the Microsoft Filter Pack or through other distributors

The search service runs on one or more servers in the farm, depending upon the servers you select during deployment and configuration. Search consists of search query and index roles. Search queries are performed using the network service account, or another account selected during installation. A separate content access account is used when crawling content sources and indexing content. A small set of administration tasks are available to site collection and farm administrators.
People using a site collection type search terms into the search box, and select a search scope from the dropdown menu. Search results appear in order of relevancy.

MOSS Search

High Level Search Concepts: Essentially, there are two main components of search: the indexing and the querying. The indexing is the process in which all documents and content are reviewed and many key items about the item (meta data) are stored. The querying is when a user wishes to search for an item. The user enters keywords or phrases and the query engine looks at the indexed content and returns items that match. The indexing process is called “crawling” and the indexed content is called “crawled content.” The querying and the query results (search results) is the end-user experience of the MOSS Search capabilities. Usually in a MOSS farm, there is one server dedicated to perform the indexing and the querying, however, these functions may be split out onto two separate servers.

In Office SharePoint Server 2007, search results are delivered quickly and relevance is tuned for enterprise and line-of-business data.

- Relevance is tuned for enterprise content with the best results across structured and unstructured data sources determined by a rich and broad range of factors.
- Robust security, granular administrative controls comprehensive monitoring, analytics, and reporting help ensure compliance and protect intellectual property (IP).
- Enterprise-grade scalability, extensibility, and manageability meet the needs of even the largest organizations.

Office SharePoint Server 2007 provides out-of-the-box search for common enterprise repositories and file types as well as for people and experts. With Office SharePoint Server 2007, you can:

- Search file shares, Web sites, SharePoint sites, Exchange Public Folders, and Lotus Notes databases out of the box and easily extend search to third party sources and file types.
- Index, search, and intelligently display information from line-of-business applications, relational databases, and other structured content using the Business Data Catalog.
- Leverage "people search" capabilities to find people not only by department or job title but also by expertise, social distance, and common interests.

Enterprise search functionality is integrated with the collaboration, portals, content management, forms and business intelligence features of SharePoint Server 2007 and can be integrated with other 2007 Office system products to help users easily find, use, and share information and increase productivity.

- Find, use and share information in the context of where you are working with the familiar tools you use every day.
- Results are displayed more clearly, hits are highlighted, duplicate entries are collapsed, and synonyms are suggested.
- Results are actionable and further enhanced through optional integration with tools such as real-time communications.

In Short,
WSS 3.0 Search Single Site collection, automatically scoped to current site (and subsites):
Only SharePoint content in the site collection can be crawled. You cannot configure Search to crawl databases, mail servers, application servers, or Web sites and file shares outside of the site collection. In a deployment with more than one site collection, each site collection provides Search only for content on that site collection, and there is no aggregation of search results across site collections.
MOSS Search
MOSS uses an enhanced relevance algorithm for its search engine, and is able to crawl content from multiple sites within an enterprise, as well as non-sharepoint web sites. In short, the MOSS search engine is a powerful enterprise search engine with a relevance algorithm, while the WSS site-local search engine is actually pretty useless beyond simple "dumb keyword" search.

Reference:
http://office.microsoft.com/en-us/sharepointserver/HA101748761033.aspx

http://www.rightpointconsulting.com/community/blogs/viewpoint/archive/2008/04/28/sharepoint-search-exposed-wss-3-0-search-vs-moss-2007.aspx

The difference between Site Master Page and System Master Page

2009-10-09T02:48:00.000-07:00

Site Master Page: The site master page will be used by all publishing pages.
System Master Page: Use the system master page for all forms and view pages in this site.

Look at the Page directive in master page, MasterPageFile setting that will usually be one of the following:
"~masterurl/default.master" means the page is using the system master page
"~masterurl/custom.master" means the page is using the site master page

Refer:http://msdn2.microsoft.com/en-us/library/ms476046.aspx

Document Information Panel

2009-09-09T06:34:00.000-07:00

Often in document management systems, users are asked—usually at the point when they are saving their documents—to provide metadata (properties) for their documents. In many cases, users don't give the request any serious consideration, perhaps because of the placement or timing of the request. Document information panels are designed to enable users to specify all the properties on a document at once, in one place, at any point when they are working with that document.

A document information panel is a form that is displayed within the client application, and which contains fields for the document metadata. Document information panels enable users to enter important metadata about a file anytime they want, without having to leave the Microsoft Office system client application

Text : http://msdn.microsoft.com/en-us/library/ms550037.aspx
Video: http://msdn.microsoft.com/hi-in/office/dd550749(en-us).aspx

Policy Features

2009-07-24T05:27:00.000-07:00

The types of policy features are

1. Expiration :
The expiration policy specifies how long to retain a document in the Records Center and what should be done with the document at the end of its life cycle

2. Auditing :
The Auditing policy enables you to audit log events and operations performed on documents

3. Labeling :
Labeling policies apply a formula to generate searchable text areas. The formula can include static text and document metadata

4. Barcoding :
The Barcode policy target problems specific to records managers concerning the consistency of physical records or documents with their electronic counterparts.

Content Type

2009-07-24T05:15:00.000-07:00

Content Type is an object stored within MOSS 2007. Content Type includes

1. document templates
2. columns that contain related metadata
3. workflows
4. information management policies
5. conversion types

Server Security

2009-07-03T09:10:00.000-07:00

Authentication mechanisms

1. Basic Authentication
2. Anonymous Authentication
3. Pluggable Authentication
4. Kerberos (Windows - integrated) authentication
5. NTLM (Windows - integrated) authentication
6. ASP.NET forms authentication

Services provided by SSP

2009-07-03T07:44:00.000-07:00

Some key service provided and managed by SSP are

1. Full text and property indexing
2. user profile
3. Single sign-on
4. Notifications and alerts
5. Business Data Catalog

Deploying the farm environment

2009-07-03T06:49:00.000-07:00

The stages for the deployment and configuration of server infrastructure are:

1. Preparing the database server and the database
2. Running the setup on each server in the farm
3. Running SharePoint products and Technologies Configuration Wizard.
4. Creating SSP

How to create a custom e-mail alert handler in Microsoft Office SharePoint Server

2009-06-18T06:53:00.000-07:00

To customize the email alerts sent from SharePoint we need to intercept the e-mail alert and modify it using IAlertNotificationHandler interface.

Refer to the below URL
http://support.microsoft.com/kb/948321/en-us

Debugging Custom Timer Jobs

2009-05-25T06:19:00.000-07:00

You can debug timer jobs by using Visual Studio just as you would any other managed application. Timer jobs are executed by a special Windows service that is set up on the server when you install Windows SharePoint Services: the Windows SharePoint Services Timer. This service triggers the executable Owstimer.exe. You must attach to this process to debug custom timer jobs.

Rename discussion board reply link name

2009-05-11T07:29:00.000-07:00

How to rename the reply link 'Reply' to 'Comments' in the Discussion board (MOSS 2007)?

1. Open the Schema.xml from 12\Templates\Features\DiscussionsList\Discuss

2. Locate ReplyNoGif field

3. Check the resource file mapped to the field and update the value of resource name ReplyLinkText as 'Comments'.

4. Save

Webpart connection

2009-04-06T09:41:00.000-07:00

Webpart connections menu will list all the webparts in the page that uses the same Interface.

Features of Sharepoint

2009-04-06T03:46:00.000-07:00

Check the Capabilities of MOSS
http://www.microsoft.com/sharepoint/capabilities/default.mspx

What is Sharepoint Server
http://www.microsoft.com/sharepoint/prodinfo/what.mspx

Product Comparision Chart
http://download.microsoft.com/download/1/d/c/1dc632e8-71e1-466f-8a2f-c940f1438e0a/SharePointProductsComparison.xls
This Excel file will give you an idea of the features MOSS support

- Syndication (RSS and ATOM) - Yes and Inbuilt support for RSS and how to Manage RSS
http://office.microsoft.com/en-us/sharepointserver/HA100214251033.aspx
- Support to Web Clipping - Yes
- Implement different kinds ok workflows, for example to approve some content update and this has to be approved - Supported

You can use Inbuilt Workflows or Create Custom Workflow using Sharpoint Designer / Visual Studio

see Developer Introduction to Workflows for Windows SharePoint Services 3.0 and SharePoint Server 2007
http://msdn.microsoft.com/en-us/library/aa830816.aspx

- Support for most know Web Browser (Is there any identified problem with anyone)
See - http://www.andrewconnell.com/blog/archive/2006/05/17/3115.aspx and http://technet.microsoft.com/en-us/library/cc263526.aspx

- In-Built Statics
http://technet.microsoft.com/en-us/library/cc262541.aspx
and You can Use Sharepoint Designer for Site Statistics ( Sharepoint Designer is Free Now www.microsoft.com/spd )

http://office.microsoft.com/en-us/sharepointdesigner/HA101741361033.aspx and here http://www.bluedoglimited.com/SharePointThoughts/ViewPost.aspx?ID=129
- autoeliminate bot traffic

- integrate easily custom security (any experience with this)
http://technet.microsoft.com/en-us/library/cc262331.aspx

- Taxonomy support for searching within sharepoint
http://blogs.msdn.com/ecm/archive/2007/01/22/taxonomy-tagging-starter-kit-for-sharepoint-server.aspx http://www.mindsharpblogs.com/bill/archive/2006/07/06/1196.aspx

- Metadata management
Managing Enterprise Metadata with Content Types -
http://go.microsoft.com/fwlink/?LinkId=101604&clcid=0x409

To Know More Check this Link
http://sharepoint.microsoft.com/blogs/GetThePoint/default.aspx
and this site discuss these features

Branding
Building Solutions
Business Intelligence
Business Processes
Calendaring
Collaboration
Compliance
Design
Education
Feedback
Lists and Libraries
People Wrangling
Planning & Process
Productivity
Publishing
Search
Site Admin
Social Networking
Team Sites
Training
Web Parts

--Source,
blog

2007 Microsoft Office System – Learning Portal

2009-04-03T08:35:00.000-07:00

The Microsoft Office Online Web site hosts additional learning resources for the 2007 Microsoft Office system, as well as templates, job-aids, special offers, and links to a community of Office users that you can participate in to extend your productivity.
http://www.microsoft.com/learning/office2007/default.mspx

http://go.microsoft.com/fwlink/?linkid=66672&clcid=0x409

http://go.microsoft.com/fwlink/?LinkId=67626

http://go.microsoft.com/fwlink/?linkid=67705&clcid=0x409

http://go.microsoft.com/fwlink/?linkid=67721&clcid=0x409

http://go.microsoft.com/fwlink/?linkid=67722&clcid=0x409

http://go.microsoft.com/fwlink/?linkid=67720&clcid=0x409

Configuring Single Sign-On Services

2009-04-03T08:21:00.000-07:00

You must complete four steps to configure the Office SharePoint Server 2007 Single Sign-On Services.

To configure Single Sign-On Services

1. The first step to configuring Single Sign-On Services is to use the SharePoint 3.0 Central Administration Web application to complete the Enable SSO in the Farm task that is created after Office SharePoint Server 2007 has been installed. This task involves managing the Single Sign-On Administrator Account and the Enterprise Application Definition Administrator Account settings for determining who can administer and create Single Sign-On applications.

2. The next step is to manage the encryption key that is used to encrypt user information and passwords. The encryption key protects the information stored in the Single Sign-On database.

3. You can then add enterprise application definitions to the Single Sign-On Service. For example, you can provide connection details and descriptions for line-of-business applications.

4. Finally, you can add details of user accounts for accessing the enterprise applications, and you can map those credentials to Office SharePoint Server 2007 users

--Source
Microsoft Elearning

Creating and Configuring Policies for Document and Records Management

2009-04-03T08:04:00.000-07:00

A policy is a set of rules for a specific type of important content.
Policies can be used to control and evaluate

- who can access the information,
- how long to retain the information, and
- when and how to discard information that must be destroyed.

Policies are usually added to lists and document libraries by compliance officers or records managers. Office SharePoint Server 2007 includes predefined policies that non-developers can use for a number of common scenarios, such as records retention, records expiration, and auditing. Office SharePoint Server 2007 also includes policies for document barcodes and official labels.

--Source
Microsoft Elearning

Create custom page layout

2009-03-31T09:03:00.000-07:00

1. Create custom site columns for the custom page layout under new custom group

2. Create a site content type for page layout under new content group

3. Add the custom site columns created to the newly created site content type.

4. Launch SharePoint Designer and open the site

5. The custom page layout must reside in master page gallery

6. Create File --> new --> SharePoint Content --> SharePoint Publishing --> Page Layout

7. Select and create the Content groups and type

8. After adding the page, go to design view, and add the fields available under the Toolbox "SharePoint Controls" --> Content Fields

9. Save

10. Now the new custom page layout is available in the site page layouts (Site Actions --> Create Page)

SharePoint BDC

2009-03-31T05:20:00.000-07:00

BDC can be used in SharePoint

1. Directly using BDC web parts
2. As SharePoint Lists
3. In Search
4. User Profile Data
5. Expose as a Web Service for other applications (Programmable API abstracts all the LOB data souces to a single and easy to use runtime object model)

-- Source
winsmarts.com

SharePoint - Approach

2009-03-27T09:15:00.000-07:00

If we wanna do a task or resolve a problem in SharePoint, the approach should be in the given order

1. Browser -- Lets start with a browser and see if we can deliver the solution using point & click

2. SharePoint Designer -- Have a lot more stuff then you would do through the browser

3. Visual Studio 2005 --- Final resolve if something that cannot be done in browser and designer.

--Source
dnrTV, winsmarts.com

Web part Zones

2009-03-27T06:11:00.000-07:00

Web part Zones live in the ASP file (eg: default.aspx) and not in Master pages, So ideally we can create various templates for the various pages, one template could have 2 web part zones and other could have 3 webpart zones or columns.

--Source
dnrTV, winsmarts.com

Shared Services Provider (Unprovisioning)

2009-03-23T01:53:00.000-07:00

Cannot delete Shared Service in Sharepoint Central Administration, and the SSP is displayed with the message “Unprovisioning”. Run the below command to fix this issue

stsadm -o deletessp -title -force

SharePoint Designer 2007

2009-03-02T01:23:00.001-08:00

The following article will show about User permissions and permissionlevels to customize SharePoint using SharePoint Designer 2007

http://blogs.msdn.com/sharepointdesigner/archive/2008/11/25/locking-down-sharepoint-designer.aspx

Some parts of your personal site cannot be created. Contact your site administrator for more information.

2009-02-23T04:29:00.000-08:00

When creating my site....

Error: Some parts of your personal site cannot be created. Contact your site administrator for more information.

Cause: Inappropriate security account

Resolution: Update the security account for the personal sites.

IIS > Appropriate application pool > Properties > Identity > Provide appropriate account

Access denied when navigate to Shared Services Administration

2009-02-17T05:37:00.000-08:00

When you cannot access the Shared Services Administration page make sure you have been added as an administrator for the respective SSP site collection.

Central Administration > Application Management > Site Collection Owners

Select the site collection of the Shared Services and add your ID/Name.

Click OK to submit.

Import Outlook Calendar to SharePoint

2009-02-04T04:39:00.000-08:00

For Outlook 2003 Users:

1. Create a new calendar list on your SharePoint site. You can do this by clicking Site Actions > View all Site Content then...
click Create
And select Calendar

2. Now that our blank calendar is created we can now work on getting the items imported Open your Microsoft Outlook Calendar and copy the Public Folder by
(a.) right-clicking on the Calendar Icon and
(b.) copying it into a new folder called "Calendar Copy" located in your mailbox folders (you will have to create this folder before copying).

Above: Depending on how old the Calendar and its size it could take 2-20 minutes to copy.

3. Export your Outlook Calendar into a Excel file format with the following columns:
· Subject
· Location
· Start Date
· Start Time
· End Date
· End Time
· All Day event
We can do this by selecting the "Calendar copy" folder that we just created and clicking
File à Import and Export

This will bring up the Wizard view . Select Export to a file

Now select Microsoft Excel 97-2003

Select the location you wish to save the file.

This will bring up the date range configuration popup. Select the appropriate dates.

Confirm the actions and finish the Wizard.

4. Now that your data is in the Excel file let's open it up and see what's in there. At this point you will notice the Start Date and End Date are in two separate columns. Now before we do anything to this data we will need to go back to the blank Calendar list in SharePoint and switch to All Event View. You can do this by entering the list and clicking Modify View àAll Events View

5. Export this empty view to a Excel Spreadsheet and open it. You can do this by clicking
Actions à Export to Spreadsheet

6. Open this exported Outlook Calendar, merge Start Day and Start Time to a single column.
You can use a formula similar to: =CONCATENATE(B:B," ",C:C) or =CONCATENATE(D:D," ",E:E) for a blank column in the same workbook to merge 2 column's data. The "B:B" is the column containing the Start date, the " " adds a space, and the "C:C" is the End Date. If your data is in another you must column change the letters correspond to the appropriate column.
Above: In the image above you can see column M and N hold both Start/End date and times.

7. Merge End Date and End Time to another single column. Both of these two column should have two spaces between date and time and YY as year, not YYYY or 4 digits.

8. Copy all Subjects from the exported Calendar to Title column of the Calendar list. The rest are straight forward. Do not put anything to WorkSpace column since it's read-only.

9. Correct any errors if you have any and please post them within this article's comment for a solution. Then sync this list to the SharePoint calendar.

Final Result:

All items from Outlook are now on our new Calendar.
Source: www.dlocc.com/sharepoint/36-solutions/61-import-outlook-calendar-to-sharepoint.html

Regular Expressions - Samples

2009-01-30T04:38:00.000-08:00

1. Area Code : "^(\d\d\d)$"
Eg: 080, 044

2. Country Code: "^\d{2,4}$"
Eg: 91, 011, 1234

3. City : "[a-zA-Z].$"
Eg: Chennai

Configuring and Extending Search for Portal Solutions

2009-01-07T07:16:00.000-08:00

Portal administrators usually customize the Search Center by adding and configuring Web Parts.For example, a typical Search Center page might include a

a. Core Results Web Part,
b. a People Results Web Part,
c. a Query Summary and Statistics Web Part,

d. an Actions Web Part, and

e. a High Confidence Results Web Part

The following code illustrates how to construct and issue a query using object model

Shared Services

2009-01-07T07:04:00.000-08:00

A shared service is an application service that is shared across Windows SharePoint Services 3.0 applications. Shared services can be included in Office SharePoint Server 2007 sites.

Examples of shared services include:

Microsoft Excel Services that provide access to server-side Excel data and functionality to multiple solutions.
User profiles that support the storage and reuse of information about users in multiple sites.

Extending MOSS Solutions

2009-01-07T06:06:00.000-08:00

In Microsoft Office SharePoint Server 2007, there are many opportunities for you, as a developer, to extend the functionality of these features. By developing components and services, you can create specific custom solutions.

In portal solutions, for example, you can develop

1. Custom Web parts to provide specific functionality.
2. Customized components for the business data catalog, and
3. Custom search components and solutions.

In business intelligence solutions, you can develop

1. Custom Web parts that are specific to the business intelligence dashboards of your organization,
2. Components that extend the Analysis Services and Excel Services that are provided by Microsoft SQL Server and Office SharePoint Server 2007.

For Web content management solutions, you can develop

1. Custom converters and field controls that enable your application to handle specific content types and authoring processes.

In records management solutions, you can

1. Create components, templates, and policies that are specific to the vertical industry of your organization, or to that of your customers.

In addition to extending and developing features for the four main areas, you can also develop custom workflows and configure other shared services that provide functionality for all types of solutions. For example, you can develop server-side InfoPath forms for data entry, and you can create specific extensions for the Single Sign-On service.

Source: Microsoft Learning: Extending Office SharePoint Server 2007 Solutions

SharePoint Fundamentals

2009-01-02T07:42:00.000-08:00

Microsoft Office SharePoint Server 2007 can be used to build four main types of applications:

1. Portal solutions,
2. Business intelligence solutions,
3. Web content management solutions, and
4. Records management solutions.

Office SharePoint Server 2007 provides many configurable features that can be included in these types of solutions.
You can adopt an assemble-and-configure approach to incorporate specific features that your organization requires when you start to build Office SharePoint Server 2007 solutions.

Building portal solutions typically includes configuring Windows SharePoint Services lists and libraries, Office SharePoint Server 2007 search capabilities, user profiles, and other shared services. Business data catalog features are also often included in portal solutions to provide business process functionality and access to line-of-business data.

Building business intelligence solutions typically includes configuring Excel Services and SQL Server Analysis and Reporting Services to provide insight into business information. In addition, many organizations require business intelligence dashboards to be incorporated into portal solutions, to provide a user interface that enables information workers to make well-founded business decisions.

Building Web content management solutions typically involves configuring the content management features of Office SharePoint Server 2007. These features include a content-authoring environment, content templates, publishing and approval processes, and content deployment features.

Building a records management solution, you will typically incorporate many of the features of Windows SharePoint Services 3.0, such as lists and document libraries. This type of solution also incorporates specific Office SharePoint Server 2007 features, such as policies, official file sites, and rights management functionality.

You can include any combination of the features from the four main application areas to build applications that are specifically tailored for the requirements of your organization.
When you have assembled and configured the features for your solution, you can extend its functionality by developing additional custom features and components.

Source: Microsoft Learning - Inside Look at Building and Developing Solutions with Microsoft® Office SharePoint® Server 2007