Keith O Hudson

Posts Tagged ‘Sharepoint’

You can use Sharepoint Designer to build a workflow that is fired manually, or automatically for new list items, or automatically for all changed items.

When I first started developing in Sharepoint, I read a lot about workflows, but had a very hard time finding anyone who knew how to build workflows in Sharepoint Designer (one developer told me you can’t do math calculations in an SPD workflow. Wrong!) and an even harder time finding out how to do the most basic tasks in SPD, so here are the basics for getting started:

1. Download and install Sharepoint Designer (SPD) (it is available free for either Sharepoint 2007 or Sharepoint 2010).

2.  Launch SPD.

3.  Connect to your site.  (File/Open Site –> then put your site name into the Site Name: text box in the format http://www.mysharepointsite.com/). You will need to provide your credentials. Its a good idea to ask Windows to remember your credentials, as they may be requested several times during a session.

4. Start a new workflow.  File/New/Workflow.  NOTE that if you hover over the NEW menu item, you can select Workflow from the shortcut menu that comes up.  If you click on NEW, you will need to navigate to the Sharepoint Content tab and select Workflow/Blank Workflow. Read the rest of this entry »

To my great dismay, I am finding that almost no one, even sharepoint consultants and sharepoint hosting providers, understand the difference between a subsite and a site collection, and why it should matter.

In Sharepoint 2007 and 2010, a Site Collection is a collection of sites sharing a common set of permissions, content types, and site columns. It was also the case in Sharepoint 2003, but according to this blog, Sharepoint 2003 hid that fact from users so they were actually using Site Collections without knowing it.

A Site Owner can break inheritance and thus manage site permissions individually on subsites, and there are sometimes good reasons to do so.  However, in a test or development environment , I would argue that it is NEVER advisable to break inheritance and have mixed permissions within a Site Collection, unless it is absolutely unavoidable for the solution you are developing.

Here’s why.  Content Type, Site Columns and Permissions are all handled by Sharepoint at the Site Collection level.  If someone working on Subsite A makes a mistake and makes unwanted changes to a Content Type or Site Column within Subsite A, those changes affect all the other subsites within that collection as well.  To return Subsite A to its default state and start over, it would be necessary to delete ALL the subsites, and recreate the entire Site Collection.

If each project is housed within its own Site Collection, such mistakes (very easy to make for someone learning Sharepoint’s out of the box features) are relatively easy to correct.

Of course, a developer who doesn’t know how to use Site Columns and custom Content Types from the Sharepoint GUI may not have this problem, but then, he or she is probably building a solution that will require you to bring a developer back in to fix the solution next time you apply a patch or upgrade to a new version of Sharepoint.

Just my opinion.  What do you think?

A week or so ago, I referred to a blog post by Shaun Young (http://tinyurl.com/GoodConsultant – opens in new window) in which he pointed out that many Sharepoint consultants don’t know what Sharepoint can really do, and end up reinventing the wheel.  I’ve decided I will start a collection of these instances when I run across them, and report them as Sharepoint Blunders — trying to do something in code that can be done through the Sharepoint GUI, for instance.

Here’s the first blunder for my collection.  While hunting for some hints on customizing Calendar lists, I came across a blog article (opens in new window) in which the author tells how to modify the Event content type in a Calendar list, to allow for different kinds of events (Event, Playgroup and Program, in his case). Read the rest of this entry »

In May 2008, Shane Young wrote a blog on The Sharepoint Farmer’s Almanac asking this very question.  (You can read it at http://tinyurl.com/GoodConsultant)  He points out the importance of the “soft side” of Sharepoint – things like usability, design, taxonomy, business analysis, user adoption, and discovery. Then comes his rant:

“<RANT> Now here comes the part that annoys me the most. If you don’t know most everything SharePoint can do out of box then don’t speak to another customer until you do! Read the rest of this entry »

From January 1999 to June 2010, I worked at America West Airlines (now US Airways), mostly as a contracts manager for the IT contracts. For two years right after the merger (2006, 2007) I did process re-engineering to bring some of the pre-merger processes together. During my entire time at AWA/USA, I have been passionate about trying to streamline and automate business processes to the greatest extent possible given the tools available, which included primarily mail merge, macros and Microsoft Access. I love computers, and I reasoned that if a business task is capable of being performed by a computer, we shouldn’t have a human doing it. Read the rest of this entry »