Microsoft SharePoint





Microsoft Sharepoint is a software platform and family of software products used for collaboration and web publishing combined. These capabilities include developing web sites, portals, intranets, content management systems, search engines, wikis, blogs, and other tools for business intelligence and collaboration. SharePoint has a Microsoft Office-like interface, and it is closely integrated with the Office suite.

Share tech news, updates, or what's on your mind.

Sign up to Post

In a Microsoft Windows IIS environment that is load balanced, the external load balancing hardware needs to know which servers, in the pool of servers, are available to send http traffic to for a particular website.

The rule, shown below, is a built in rule that requires each IIS Website on each IIS Web Server to have a http://healthcheck host header.

The load balancer will check each website using the http://healthcheck host header and look for an alive.html web page. Upon being able to access that alive.html web page, the load balancer will continue routing traffic to that particular website on that particular web server for another 60 seconds.

Using this built in rule administrators only have to add a healthcheck host header to each IIS Website.

This built in rule eliminates any need for administrators to create a separate and distinct set of rules for each IIS Website  on each Server using the websites own distinct name.

http_alove lb monitor
Now, enters SharePoint 2010 and how it is incompatible with this rule.

For the sake of an easy example, let us declare that we have three Windows 2008 R2 Servers that are running SharePoint 2010 Standard Server.

We will call them SPServer1, SPServer2, SPServer3, and they are configured as follows.
SPServer1 runs the Central Administration Console, and contains all SharePoint Websites. But end users never Access the SharePoint Websites here.
SPServer2 contains all SharePoint Websites
Note:  There are two main ways to deploy InfoPath forms:  Server-side and directly through the SharePoint site.  Deploying a server-side InfoPath form means the form is approved by the Administrator, thus allowing greater functionality in the form.  This document explains how to deploy a Server-side InfoPath form.  Also, this form is referred to as a "Full-trust" InfoPath form.

1. Copy the InfoPath template locally to one of the SharePoint web servers
2. Logon to the SharePoint web server
3. Open "Central Administration"
4. Select the "Application Management" tab
5. In the "InfoPath Forms Services" section, select "Manage form templates"
6. Select "Upload Form Template"
7. Browse to the appropriate template and select "Upload"
8. Check the "Status" of the installation
      a. Next to the template is a "Status" field.  Refresh the screen periodically until the status changes.  If the status doesn't change after several minutes, you can force the timer job to execute immediately by the doing the following:
            i. Open a CMD prompt
            ii. Browse to a path in which the STSADM.exe cmd resides
            iii. Execute the following:  stsadm -o execadmsvcjobs
            iv. This will kick off all Timer Jobs and hopefully finish the installation of your new InfoPath Template
      b. When the Status is "Ready", proceed to the next step
9. Left-click the uploaded form and select "Activate to a Site Collection"
10. Select the appropriate site …
We had a requirement to extract data from a SharePoint 2010 Customer List into a CSV file and then place the CSV file into a directory on the network so that the file could be consumed by an AS400 system. I will share in Part 1 how to Extract the Data and save it in a csv file.  In Part2, I will explain how to schedule it on a periodic basis.  

After some research I found Roi Kolbinger's blog "I Will Share my Point: Export SharePoint 2010 List to Excel with PowerShell.  The problem with this is that it will only extract the Title field.  I was able to create a PowerShell script to extract the data using Roi's script as the base for my script and with a little help from a developer, named Miguel Wood,  who told me "Yes.  The .Items will only export the Title column.  To export the list, try creating and using a PSObject."  
Now that we have some background information, let’s create a SharePoint Management Shell script to extract the data from a SharePoint 2010 List and into a csv file.

1.  Open notepad and paste the following code customizing it for your environment.
$MyWeb = Get-SPWeb "http://sitename"
$MyList = $MyWeb.Lists["ListName"]
$exportlist = @()
$Mylist.Items | foreach {
$obj = New-Object PSObject -Property @{
            “Column1” = $_["Column Name in SharePoint"]
           "Column2" = $_["Column Name in SharePoint"]                  
$exportlist += $obj
$exportlist | Export-Csv -path 'C:\FilePath\Filename.csv'
*Notes:   Http://sitename is the url to the…

Expert Comment

Hi Miguel

Thank you for your article, I will be attempting shortly.

I wondered if the following was also possible as we need to export our job data into a csv file for our accounting software which is Soloman.

We would need to filter items which have a tick box placed next to ready for invoice in the list.

Further to that, we need a column which is called invoiced which gets selected once the export has run so that duplicate entries don't get sent to the csv file.

Is this possible?

Author Comment

by:Eldrick Vance
Hello James. Thanks for taking time to read my article.  Unfortunately I do not know how to make the script do what you need.  I will do some research and see if I can assist.  


The vision:

A MegaMenu for a SharePoint portal home page

The mission:

Make it easy to maintain. Allow rich content and sub headers as well as standard links. Factor in frequent changes without involving developers or a lengthy Dev/Test/Prod release cycle. The personal assistant of the marketing boss should be able to make changes on the fly. Instantaneous. Without any knowledge of HTML or CSS, so editing code is out. If it’s more complicated than filling in a time sheet, it won’t fly. And do all that with just the browser interface and SharePoint Designer. No Visual Studio, no custom code.

What’s a MegaMenu, anyway?
There are quite a few sites out there describing how to create impressive MegaMenus if you Bingle a bit. Rave reviews of the concept from Jacob Nielsen. Flashy sites from developers strutting their stuff. JavaScript, jQuery – the choice is yours. Most of them even work.

None of those take into account a SharePoint background, though. The MegaMenu content is always somehow “there already”, nicely configured in a nested construct of UL and LI tags, with hard-coded <A href> tags and titles. Not something the Marketing Assistant will want to get his head around if he wants to add a few items and a flashy “Hot and new” icon to a new menu entry.

So, to achieve the vision and make the mission possible, we need to come up with some practicable steps.

Here’s the plan:

Create a SharePoint list that stores all the items to feature in the MegaMenu
LVL 50

Author Comment

by:Ingeborg Hawighorst (Microsoft MVP / EE MVE)
Köbes? Eine Runde für Tolomirs Tisch!
LVL 50

Author Comment

by:Ingeborg Hawighorst (Microsoft MVP / EE MVE)
As is the way with the internet, sites get created, sites get abandoned. Links die.

The link in my above article to the demo of the MegaMenu has died.

Fear not. The Wayback machine comes to the rescue. Here are the links to the content that does not work anymore from the links above.

MegaMenu Demo

Background on the MegaMenu CSS and HTML structure

cheers, teylyn
SharePoint Designer 2010 has tools and commands to do everything that can be done with web parts in the browser, and then some – except uploading a web part straight into a page that is edited in SPD. So, can it be done?


For a recent project I created a Content Query Web Part (CQWP). To fine-tune the data presentation I used customised XSL templates. Good practice suggests that these templates should not be stored in the default ItemStyle.xsl and ContentQueryMain.xsl, but in separate files. I did that and then exported the web part and edited the .webpart file to link to the custom XSL files. Then I uploaded the .webpart file to a web part page via the browser interface for testing. All good so far.

As a next step I wanted to integrate this customised web part into a Page Layout, so that new pages created with that layout would always include the customised CQWP. I did not want to use a web part page, for the following reasons:

Users with edit rights would be able to accidentally delete the web part from the page
I wanted the ability to quickly create new pages with the same layout and CQWP, without having to manually upload it into every new page
I did not want to store custom scripts calling CSS and jQuery functions in a Content Editor Web Part, but integrate them in the page header instead.

So, off we go: fire up SharePoint Designer 2010. Create a new Page Layout, create a structure with …
LVL 50

Author Comment

by:Ingeborg Hawighorst (Microsoft MVP / EE MVE)
Thanks, younghv.

Expert Comment

good , and Thanks


In SharePoint 2010 it is easy to create custom color themes to jazz up a site. Theme colors can also be created in PowerPoint 2010 with a few clicks. But how do the chosen colors actually look in the SharePoint site? The attached PowerPoint has a preview of all the main elements of a SharePoint 2010 site with the selected color theme.


Using Office Themes for SharePoint 2010 sites is easy, but can be time consuming. You need to create new theme colors in PowerPoint, save the file as an Office Theme with the .thmx extension, upload that theme to your SharePoint site collection gallery, and select it in the site via Site Settings > Site Theme.

The Site Theme page has a preview button where the site landing page is then displayed in the new theme colors, but there are a few drawbacks:

chances are that this page does not show all the site elements that are affected by the theme changes
you cannot click through to another page of the site to check the new colors there
the preview is slow to generate
some site elements, for example the list form backgrounds, use shades of the main accent colors, and you could end up with a lot of trial and error time until you finally arrive at the desired color effects for all site elements
the preview is buggy (it often throws an error in my environment and also often just does not display the correct colors)

Pimping Sharepoint 2007 without Server-Side Code

Part 1

One of my biggest frustrations with Sharepoint 2007 in the corporate world is that while good-intentioned managers lock down the more interesting capabilities of Sharepoint programming in the name of sustainable code, they often kill innovation in the process.  Over the last several years, I have had the opportunity to find ways around this strict no-code policy to achieve a user experience that is reasonable while getting all the benefits of Sharepoint 2007.

In this series, I will show you how I have leveraged the existing infrastructure of Sharepoint along with the out-of-the-box  Content Editor Web Part and jquery to give Sharepoint a much nicer look and feel, users more natural access to the data, and ultimately design freedom within the walls of a Sharepoint installation.

I will be making a lot of assumptions about the reader’s experience with Sharepoint and jquery.  You should be able to make and manage lists, created libraries, and all the other “normal” Sharepoint administrative tasks that occur through the interface.  You should also have a pretty strong working knowledge of the jquery core.  If neither of those are in your wheelhouse, this article might not be for you.

Getting Started
You must have Sharepoint 2007 installed and have Full Control on a site collection.  If neither of these is true, stop reading now.  The rest of this article won’t matter to you.  

We’re going to …
LVL 56

Administrative Comment

by:Mark Wills
No worries.

I can see your question :

Hope you also have a great weekend...
LVL 16

Author Comment

by:Steve Krile
Was just reading through this article a few weeks ago and it bothered me how aged it had become. I've learned a ton about this approach and am now using Sharepoint 365. Also, writing articles is really time-consuming so I'm switching to an episodic video format. You can check it out here.
Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010 do not offer the option to configure the location of the SharePoint diagnostic trace log files during installation.  This can, however, be configured through Central Administration or through a simple PowerShell command after installation.  

With the default SharePoint configuration, the SharePoint diagnostic trace logs are stored in the 14 HIVE on the local hard drive of each SharePoint server in a SharePoint farm (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS).  If you are not going to store the diagnostic trace log files on a different drive, it is recommended to leave the default location.  However, you may wish to store them on a different local hard drive for storage space or other considerations.  

When deciding where to place the SharePoint diagnostic trace log files, it is important to remember that they must be stored on a local hard drive.  SharePoint does not support storing the diagnostic trace log files on network storage.  Also note that the specified directory location must exist in the same place on all SharePoint servers in the farm.

To configure the SharePoint diagnostic trace log location through Central Administration:


Open Central Administration for the SharePoint farm you wish to change the storage location for


In Central Administration, browse to Monitoring and then to Configure Diagnostic Logging under Reporting



Expert Comment


I found you can change the INDEX LOCATION during installation.
SharePoint Index File Location During Install
However, the DIAGNOSTIC LOGGING.....I haven't found. This seem to be done after only.


For SharePoint sites, particularly public-facing ones, there are times when adding JavaScript, Meta Tags, CSS Styles or other content to the page <head> section is more practical than modifying master pages.  For instance, you could add the jQuery library to the head of every page.  If adding tags to the page <head> section is the only customization being made side-wide, doing so programmatically instead of modifying and un-ghosting the default master pages will increase the performance of the site.  (Un-ghosting a page means that SharePoint is no longer grabbing the master page from the local hard drive and is instead grabbing it from the Content Database.  This adds another call to the database that isn't necessary unless you have a fully branded master page).

To demonstrate how to accomplish this programmatically using the AdditionalPageHead Content Place Holder, we will make a SharePoint solution in Visual Studio 2010 that adds a custom JavaScript file and a custom CSS file.  This solution could be further extended to dynamically add different content based on configurable settings, however for this demonstration we will keep it simple.


Open Visual Studio 2010 on a computer running SharePoint 2010.


Select File > New Project.


Make sure .NET Framework 3.5 is selected.


Under Visual C# > SharePoint >2010, select Empty SharePoint Project.


Provide a name and location for the solution, for the demonstration we are using CustomPageHead.


There is one common problem that all we SharePoint developers share: custom solution deployment.

This topic can't be covered fully in this short article, so all I want to do in this one is to review it from a development-to-operations perspective.

This is the problem statement:
You have your SharePoint solution developed and ready to be delivered to the production environment (I'm intentionally skipping all the QA steps here). All you have is one or more WSPs (as you may know, WSP is a CAB-based package containing solution files and XML manifest with instructions to SharePoint how to deploy solution files) and some features of different scope inside. But in my experience, this is not enough to get your solution deployed even on a test environment.

Most of us, old-school SharePoint developers, used to write STSADM-based batch files to automatically deploy, install and activate; but this approach is not very convenient: no logging, no UI, and too much preconditions to have it successfully completed.

Almost the same experience is regarding PowerShell. Please note that I'm referring only deployment automation aspects of using PowerShell. No doubt that PowerShell is a great tool for a lot of IT tasks, but it gives almost the same user experience when used for SP deployment automation.

The next approach is usually to write a proprietary tool to take care of deployment.  If used for many different solutions, such a tool could become …
I used to be SharePoint evangelist in our company, so my Outlook always full of questions about how to do this, or where I can find that. One day I found such an email with the following question: "how to attach 3-State workflow (one of the workflows available "Out-of-the-Box") to the Wiki Library".

Looks like a good idea for business users, especially if they need to control wiki content contribution. I have to mention that their department use small isolated SharePoint farm based on MOSS 2007 Standard.

As usual, I sent her simple step-by-step manual from the MS TechNet (or someone’s blog article, I don't remember the exact source).

She has successfully attached workflow to the library, assigned column with state values, and managed to start the workflow without any problems. Although all the workflow instances she started have never been finished successfully. That became interesting for me so I visited her servers myself. After some diving into logs I found the following exception:

System.ArgumentException: Value does not fall within the expected range.     
at Microsoft.SharePoint.SPFieldCollection.GetField(String strName, Boolean bThrowException)     
at Microsoft.SharePoint.SPListItem.GetValue(String strName, Boolean bThrowException)     
at Microsoft.SharePoint.SPListItem.GetValue(String strName)     
at Microsoft.SharePoint.SPListItem.get_Title()     
at Microsoft.SharePoint.Workflow.Application.IssueTracking.OnWorkflowActivated(Object sender, 

Open in new window

If you create your solutions on SharePoint sooner or later you will come upon a request to set  permissions of the item depending on some of the item's meta-data - the author, people assigned as approvers, divisions, categories etc.

The most natural way to tackle such request would be to have a event-handler or a workflow running when item is created or modified and modify current item's permissions. It very simple with any workflow solution - you just need to use the "set item permissions" activity.

If you deploy it on some small list (up to 50 items) with small number of users (4-5) then everything will work fine. If you try to implement it on larger list (few thousand items) with larger number of users then you may run into serious performance issues. You can experience long page load times, very high load on the SQL processor, timeouts for queries, IIS and OWS Timer unresponsiveness and workflow crashes.

The information about unique item permission limits can be found:
- here for 2007 -
- and here for 2010 - 
(look for the "Security scope") but it's worth clarifying what it exactly means.

For both SharePoint 2007 and 2010 there are limits of 1000 unique security scopes for a list. Microsoft defines a security scope as a "security boundary for a securable object and any of its children that do not have a …
I recently came across an issue with a MOSS 2007 deployment where access into some sub-sites were denied, even for the MOSS farm administrators.

A bit of background to the setup of this MOSS farm; this was a three server setup, consisting of a front-end MOSS web server, back-end SQL 2005 server and server system containing search, indexing, single sign-on, amongst other back-end MOSS services.

The farm administrator had attempted to access one of the sites in question, receiving an "Access Denied" page, then attempted to change permissons to the site by accessing the site with a farm administrator account, still receiving an "Access Denied" message.  The predicament was further exacerbated as the primary administrator of the site, had left the organisation and account had been deleted many months prior.  The administrator had attempted to visit "/_layouts/mngsiteadmin.aspx" for the site, which will show the admins for a site. If only one admin has access they can add more admins and save, but in this instance was still receiving an "Access Denied" page.

The tip to solving this issue is to alter the site collection administration, from the MOSS Central Administration website.  This can be achieved as follows:

1.       Go to MOSS Central Administration as a farm administrator

2.      Navigate to Application Management

3.       Under “SharePoint Site Management”, you will find “Site Collection Administrators”

 Site Management
4.       The important …
The Scenario: Let’s say you have a quote worksheet in Excel that you use to work up sales figures and such for your clients. You utilize SharePoint to manage and keep track of these documents. You would like values from your worksheet to populate SharePoint properties in the document library. For instance, you would like the Quote Date and Quote Amounts to populate in the SharePoint properties for the document.

Out-of-the-box there isn’t a simple way to make this happen. You can view and edit the Document Properties from SharePoint in Excel, but there isn’t a straightforward method of setting those properties from values within your Worksheets. We can, however, accomplish this by using a very simple VBA (Visual Basic for Applications) script.

If you are reading this tutorial, I assume that you are using SharePoint 2007 or SharePoint 2010 with Excel 2007 or Excel 2010 and have a basic understanding of working with both document libraries in SharePoint and with Excel spreadsheets. I will include some links to other tutorials if you are unsure how to complete certain steps.

Here’s how to add the VBA script to accomplish this:


In SharePoint, create a new Document Library. (For help:


Add a new Column to the Document Library called “Quote Amount” and set the column type to Currency. (For help:



Expert Comment


What if I wanted to populate an excel worksheet cell (which is an excel template / content type for Purchase Orders) with the Purchase Order number associated with the item via an SPD Workflow?


Expert Comment

what if I want the url of the document library? how do I grab that??
When installing SharePoint 2010 RTM I came across a strange error, I was getting timeouts during the installation.

I searched the web and found the best solution to be found here.

Becasue there are several fixes on this blog I have included the part that works for me:

It seems like it is happening because of the service account.  I was trying to do this on my virtual machine's DC, and it got stuck since it was pointing to Local Service account. The moment I changed it to Local System, the configuration zipped through. I tried the same thing twice, and it worked fine both the times. So, the trick is to run the PSConfigUI.exe and the moment you get to the SharePoint Search service, switch back to the Services console, change the user to Local System, and restart the service. The installation succeeds after that.


Basically SharePoint install deletes and recreates the registry entries for these Services and assigns Local Service Account .  This account does not have the necessary authority and therefore stops.  You need to change the services to have the correct account type inflight, when it stops at installing the two services...

There are two Services that this applies to:

SharePoint Foundation Search Service and
SharePoint Search Service

This caused me hours worth of issues until I found the post as noted.

Last week I faced a strange issue recently, i have deployed SharePoint 2003 servers for one project and one of the requirements was to open SharePoint site from same server. when i was trying to open site from the same server i was getting authentication prompts and the site was not opening. I have even added the URL entry in the local host file but the issue remains same. After googling i found one Microsoft KB on the same issue which stated that  “This issue occurs if you install Microsoft Windows XP Service Pack 2 (SP2) or Microsoft Windows Server 2003 Service Pack 1 (SP1). Windows XP SP2 and Windows Server 2003 SP1 include a loopback check security feature that is designed to help prevent reflection attacks on your computer. Therefore, authentication fails if the FQDN or the custom host header that you use does not match the local computer name.”

In order to fix this we need to disable loopback check on all web servers which are facing this behavior. I have applied this fix on my both front-end servers and after restarting both front-end servers i have checked and the issue was resolved . I can now open my portal website on same front-end servers. Following is the fix i followed.

Method 1: Disable the loopback check
ref :

•Click Start, click Run, type regedit, and then click OK.
•In Registry Editor, locate and then click the following registry key:

Author Comment

by:Khurram Ullah Khan
The MS KB is general and not specific to sharepoint. I have faced this issue in shareppoint thats why i mentioned it specific to sharepoint.
Work Over Net is a new and very powerful collaboration product. With its new easy interface it is becoming very competitive to other similar products like webex and office interactive. WON 2010 have the standard business tools needed for multi-office businesses, it is not specialized for IT companies like most of collaboration systems are, it has an everyday tool for every employee in any company.

As I mentioned before it has a very simple and friendly user interface, WON 2010 creators have aimed to simplify their product so even grannies can use it without the need for prior education time. That is very helpful when you have a company with thousands of employees, imagine buying a product that you need to provide an education for every person in the company to use it. Most collaboration systems are very complicated that even I need some time to learn work with it. This one is very similar to windows interface.

What WON 2010 offers?

Work Over Net 2010 have the standard tools any company need, it is a very good intranet software a company can install. You have document Manager, Announcements application, Projects Manager, Calendar, Internal Messaging System, Address Book, Forum, Full text search, Real time Chat and a To-Do List. As an Administrator you can go to administration panel, make groups and add new  users, view and edit everything in the system. Users can change their profiles, language and look of their interface, passwords and define the link for …
I have just recently built a new SharePoint 2007 farm on a complete Windows 2008 R2 server platform and part of my standard build procedure is to implement a warm up routine, usually in the form of a script that is scheduled every morning to launch my SharePoint Web Applications.  Most of you will most likely know what I am referring to here, the slowness that end users experience when loading a SharePoint site for the first time in the morning!?

By default IIS will recycle its worker processes during the night, in my case IIS 7.5 tells me this happens at 1:04 AM.  You can locate this information in IIS Manager / Application Pools / Highlight your application pool in question and select Recycling under Actions / Edit Application Pool.


So what is recycling all about?  Here is a brief primer;

Recycling is all about stopping any current w3wp.exe processes that are running for a particular Web Application Pool and starting a new one.  The purpose of this maintenance routine is to clear the cache and start afresh! This routine obviously causes SharePoint to be quite slow when accessed for the first time after the recycling process.  This is because when accessing a SharePoint Site/Page for the first time, that information needs to be re-compiled and loaded into memory again.

So what can we do about this first time slowness that occurs every morning?  Wake SharePoint up!

There are an array of scripts that have been developed by 3rd …

Expert Comment

They have removed the BETA from the IIS website

Expert Comment

@pramodsk40 if your enviroment is large enough you should have multiple web frontends.  The idea would then be to schedule maintenance mode everyday on each one of the WFE and remove it from the NLB then run to warmup scripts and place it back on to the NLB fresh and ready for action.  This will then not affect users and the server will constantly be ready.

Come to think of it though, if the servers are used 24/7 it wont need to a warmup script as it is already warm so to speak
Recently Microsoft has released the Fourth Release of the Microsoft SharePoint Administration Toolkit. It was announced on the SharePoint team blog.

A very interesting part of this toolkit is a permission reporting tool. I think that every administrator should have it on their MOSS/WSS environment as this helps with permission management on the farm. It is also really useful when working with work-flows and other permission setting solutions - it can help you debug some problems with the permissions to the work-flow and work-flow items.

Generally, the tool allows administrators to quickly check users' permissions. This is very helpful, especially when you have multiple inheritance brakes and large number of permission levels - it is very easy to lose track of who has which permissions.

The tool allows you to check permissions on every level (site, list and item) to determine what permissions the chosen user has. The tool displays what kind of permission levels the given user has to a chosen object and how they were assigned (i.e., through group or directly). More about this functionality is here.

The reporting tool, also, gives you the ability to quickly glance through permissions for all lists and sites in a given site. It also lets you compare the permissions to the parent permissions and lists which are different - who was added and who was removed as well as different permissions for given users on both locations. More on
LVL 15

Author Comment


You have a list setup just the way you want it and it now has a just over ninety thousand items in it. Now the boss decides that [insert some activity that has to impact every item separately i.e. sending an email to the stakeholder listed for every matching item with the value of one of the columns]. If only this was as simple as setting up standard reporting where a simple CAML query or Data View Web Part would suffice. Being the knowledgeable developer that you are, the first thought is to pop open Visual Studio, but in your corporate environment you don't have access to Visual Studio and definitely don't get a virtual machine to develop on.  And even if you did, it would take two months for all the approvals necessary to get your solution on the server which clashes with the boss' demand that it is completed tomorrow. Time for a workaround.


In an ideal world all list iteration would be done with Visual Studio, but I understand that some corporate environments are not conducive to Visual Studio usage so here is the way to do it with SharePoint Designer. Please note, only use this if you cannot create a Visual Studio workflow.


In the list you want to iterate through (named Example for this) create a new column to be used as check. This can be pretty much anything you want since you will be changing it manually with the workflow. For this example I will assume a choice column named Iterate with X and Y as the options.



Expert Comment

thats a really useful article.

Expert Comment

by:Snehal Rana
First of all great article. I am working on similar requirement to create a for-each loop to update multiple List items. On your Step 4 you want to start a workflow. Which list are you referring to? Main list where all the items are or the Taskmaster list?
A question that is asked often, is how to generate sequential numbers in InfoPath Forms. The best way to achieve this is to use a SQL database, along with a stored procedure and a web service to connect Forms Services to the DB.

The first thing to do is create a database table to store and update the numbers. Please see the image below.

Image 1
The database needs nothing fancy, just a column I called CurrentNumber. The column type is an integer. I called the database table tblSequenceNumber.

The next thing to do is create a stored procedure that will be used to update the number. This will be a middle man between the web service we will create later and the numbering database. The stored procedure should look something like this:

Stored Procedure
As you can see, the stored procedure is now called spGetNextSequenceNumber.

The next step is to create a web service that will allow InfoPath/SharePoint to talk to the DB without running into any double-hop or authentication issues. Without the web service, this would not work. The web service should look something like this:

Web Service
The web service will now connect to the stored procedure and update the number DB incrementally. The webservice should be called something.asmx and stored in the following location on the front end server(s):

%Program Files%\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\Webservices

Now we get to the fun part. …

Expert Comment

by:Dr.Abdulwahab Al-anesi

Expert Comment

by:Jason Baker
Can this method be adapted for SharePoint 2013?
This example will use a custom field type to create a drop down list populated from a Sharepoint List.

There are four main components to building a custom field&

"      Field Class* This must inherit from an existing SPField class. e.g. SPFieldText. It handles custom validation for the field, as well as defining the Field Control used to display it.
"      User Control Rendering Template.  This defines the control to be used to display the custom field.
"      Field Control Class. This contains the code-behind for the user control file, and defines how the control is rendered.
"      Field Type Definition File. This contains the information that SharePoint needs to correctly render the field, as well as information about the assembly that contains the compiled field type.

The example demonstrates a custom field type designed to list all entries within an example list entitled Organisation List.

1. Field Class

Each instance of this class represents a separate field based on the custom field type. It must inherit from one of the SPField subtypes, a list of which can be found at the end of this document. The most commonly used subtype is SPFieldText, and this is used in the following example code.

using System;
using System.Runtime.InteropServices;
using System.Security.Permissions;

using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
using Microsoft.SharePoint.Security;

namespace Company.Application.Controls

Open in new window

The STSADM command is extremely useful in the management of site collections and sub-sites.  Here are a few commands that I have used in my daily SharePoint backups:

*  Back-up an entire Site Collection to a single file:
stsadm -o backup -url http://sitecollection -filename c:\site_collection_backup

Open in new window

*  Back-up one site to a single file:  
stsadm -o export -url http://site -filename c:\site_backup

Open in new window

*  Restore a site collection from that file:  
stsadm -o restore -url http://sitecollection -filename c:\site_collection_backup

Open in new window

*  Restore a site from that file:  
stsadm -o import -url http://site -filename c:\site_backup

Open in new window


Expert Comment


Does this command back up all Data Base Objects associated with the SP instance?

Expert Comment

Brilliant article!!!!!!!!1

Microsoft SharePoint





Microsoft Sharepoint is a software platform and family of software products used for collaboration and web publishing combined. These capabilities include developing web sites, portals, intranets, content management systems, search engines, wikis, blogs, and other tools for business intelligence and collaboration. SharePoint has a Microsoft Office-like interface, and it is closely integrated with the Office suite.