The SharePoint Swiss Army Knife

If you’ve ever spent anytime using InfoPath, you know how awesome this tool is. It enables you to create forms in a WYSIWYG application and even let’s you connect it to data sources. The sweetest part is that if you’re using Microsoft Office SharePoint Server 2007 Enterprise you can publish these forms straight to your server and have users fill them out via the browser! MOSS 2007 Enterprise comes with InfoPath Forms Services which renders InfoPath forms as html so you don’t have to install the client software on all of your users’ computers, although you do lose some of the richness.

I was creating some forms the other day and couldn’t figure out for the life of me how to make a multi-line textbox expand dynamically without the use of scrollbars. My scenario was that I wanted to have the users be able to fill out the form as well as be able to print the form. But if they go over their alotted # of lines, then their text won’t get printed. So I dug around InfoPath for awhile, going through all the controls and properties, then finally stumbled upon the Rich Text Box. I proceeded to feel enlightened and an idiot at the same time…

I was previously trying to use the regular Text Box but that couldn’t be dynamically expanded with browser-based forms. The Rich Text Box control uses XHTML and works great!

In case anyone else out there is working with bleeding edge tech and has to support it also, here’s a quirk I’ve come across when trying to save documents from Office 2007 applications to MOSS 2007.

Scenario 1:
– Windows XP
– Office 2007
– WSSv3/MOSS 2007

 Office 2007’s save boxes has a tab for “My SharePoint Sites.” This tab will give you links to SharePoint sites that you are a member of and also links that have been published to you. Upon clicking on the links, they work as expected taking you to its respective sites/document libraries.

Scenario 2:
– Windows Vista
– Office 2007
– WSSv3/MOSS 2007

The save dialogue boxes gives you the same options as if you were on XP except they don’t always work. Usually either an error box will pop up or you will be prompted for network credentials everytime you attempt to save a document using a new Office application session. With some help from the SharePoint community I was able to figure out a non-ideal workaround. So what I did was:

1. Create Network Shortcuts to the SharePoint sites that I wanted to save to.
2. Copy the shortcut that was created.
3. Navigate to the “My SharePoint Sites” folder which is located at “C:\Users\username\AppData\Local\Microsoft\Office\My SharePoint Sites”
4. Paste Network Shortcut into that folder.

After that everything seemed to work just fine – no more network login prompts nor errors. I know this isn’t ideal especially if you have a whole company full of Vista users but hopefully someone else comes up with a better solution sometime in the near future.

If you’re like me and you’re working with a generally non-technical company, the roll-out of Microsoft Office SharePoint Server/Office 2007 System can be quite a daunting task. I’ll try to keep the ranting to a minimum but below will be some major issues that anyone in charge of a SharePoint deployment should be aware of.

1. If you’re planning on using SharePoint as a file share replacement, interview everybody!! And don’t take no for an answer. Many document intensive companies will have cross-departmental ownership of working files and you’ll be quite surprised that there are often times nested active files and folders that many people are not aware of. To prevent the duplication of efforts or file structures, these nested file structures will have to be taken into consideration if you are planning on creating departmental sites and/or portals. I unfortunately experienced this problem as a consultant – my main project contacts were misinformed on how tightly integrated multiple departments were and therefore we had neglected to interview all of the affected groups. What resulted was the launch of their MOSS portal having a ton of team sites with semi-duplicated document library structures.

2. Another misconception is not needing to involve everybody! You cannot expect to get a SharePoint solution setup and think that it would be possible to simply push it down on an entire company without their involvement. To fully take advantage of all the awesome collaborative features, you will need feedback from not only the department heads but also the people that will be working with documents stored on SharePoint all day long. By consulting with everyone, you will be able to tailor the solution to the way they work and not to mention how much easier it will be when launch day comes around!

 3. Demo often! I’m not caught up on software engineering but I guess this would fall under one of the Agile/Scrum manifestos. If you plan on taking advantage of many of the SharePoint document management features it will be wise to constantly demo them, and not only demo them but also have your users test them out. For example, some of the main selling points of SharePoint is its ability to have document versioning, check-in/check-out, information rights management with document information panel, etc. These all sound great and dandy but may greatly lower expectations if end users are not able to experience the process early on in the launching process. They may find the check-in/check-out process too cumbersome and decide against it, which might be quite a headache if you had already created 50 sites, with 10 document libraries each, like I did…

4. Upgrade to Office 2007! If you’ll be using either Windows SharePpoint Services ver. 3 or MOSS 2007 for mainly document management then you definately want your users to have a flavor of Office 2007 to be able to enjoy the whole Office System experience. It’s not flawless, but it’s definately a must. If you’re going to be on Office 2003 or earlier, you might as well stay on the 2003 SharePoint versions.

5. Train your users! I hope this goes without saying but it has definately been one of the more difficult tasks for myself. With today’s fast-paced business, project deadlines, ever-changing technology and a company full of middle-aged non-technical end-users (sound familiar?), proper training will the key to a successful transition. So how the heck can you train everyone in preparations for a smooth transition? I’m open to suggestions if anyone has any! So far, we’ve had formal training provided for the entire company, taking a full day out of everyone’s work week. And that 8-hour training day was barely enough for them to touch upon many of the new UI changes of the Office 2007 suite. If you think that is bad, can you imagine telling your company that they can no longer save documents to a file share but now have to navigate through another set of directory listings to find the proper SharePoint site? And then they have to decide if they want to check-in the file. How about minor versions? Or do they want major versions? Oh wait, you don’t press the save button anymore, you have to go to Server > Check-In. Don’t forget to press the check-out button before you edit, oh and don’t forget to fill out the document information panel with relevant metadata….. As you can see, it can be quite confusing to most average users as to why these things need to be done. All they wanted to do was save a file right?

For me, it almost seems like a never ending tag-team battle between Me/SharePoint and Old Habits/File Shares. I hope this has given you some insight into any SharePoint adventures that may lie before you.