OneNote and Metadata in SharePoint–Connecting Related Documents to Client Names–Part 3 of 5

As described in our original scenario, we want to create a relationship between our Client list and their related documents, so that ultimately we can make a relationship between our OneNote notebook, and the related Client. We created our Client Names list in Part 2, now lets see about making the connection with the documents.
Here we have a basic document library that contains several different documents:

But how do we know which Client the Expense Report belongs to, for instance? We’d have to open the document and read its contents to try to figure it out. Wouldn’t it be nice if we could add a column that could tell us that information right in the default view of our document library? Fear not – we can!

OneNote and Metadata in SharePoint–Creating a List of Client Names – Part 2 of 5

As described in our original scenario, we want to create of list of Client Names so that we can ultimately associate our OneNote notebook with one of them.

This list can be thought of as a standard Lookup list, as well as a repository for Client information. The Client Name will be used to fill dropdowns in other list columns or forms, but also provides a 1-click way for a user to see more detailed information about a Client associated with another item. I’ll show you what I mean, but first let’s create the list. You can use any of the following methods:

• The Standard Way
• The Import Way
• The SharePoint Designer Way
• The PowerShell Way
• The Visual Studio Way
• The External Content Type with Azure Way

Choose the option that works best for you – let’s begin! (click on images for larger views):

Fake It ‘Til You Make It–Alternatives to Custom Application Pages for Non-Developers

SharePoint is a versatile tool meant to empower end-users. So, for me it seems such a shame when end-users feel powerless when it comes to their ability to ‘create’ in SharePoint. Sometimes for a non-developer, it can seem like the only way to make something interesting in SharePoint (besides a fancy list or some Wiki pages) is to get help from a Developer or Web Designer. But I submit that, with a little creativity (and maybe some smoke-n-mirrors), non-developers can make an ‘application’ that looks and feels like a Developer’s custom application page.

SharePoint Crash Course webinar with BDPA Atlanta

On Tuesday, April 3rd at 7pm EST, I’ll be delivering an online webinar for the Atlanta chapter of the BDPA as part of their Tech Talks series. I’ve got 90-minutes to give a crash course to attendees on everything that is the wonderful world of SharePoint – that’s right, from calendars to content types, from lists to libraries, from RBS to BCS.

My intent is do a 60-minute lap around the “wheel”, then wrap up with some live demo of solutions that attendees can do as soon as they get back to their office or friendly-neighborhood VPN. Q&A will also be included.

To join the webinar on Apr 3rd, 7pmEST:
   Go to URL http://www.anymeeting.com/bdpaatlanta1
   Call conference call toll free number: (218) 339-2409
   Use Attendee Access Code: 471 4295

[Update 4/4/12 – slide deck added below, and on Slideshare:]

So strap yourself in and join the ride – I’m gonna show you all the stuff you didn’t even know you didn’t know, and weren’t sure you ever wanted to know, but now you know – and knowing is half the battle.

Useful phrases for fighting SharePoint-Sucks-Syndrome

Many organizations face the challenge of good SharePoint adoption due to the battle of fighting the SharePoint-Sucks-Syndrome (not to be confused with Paul Culmsee’s SharePoint Fatigue Syndrome). SharePoint-Sucks-Syndrome is a debilitating illness that includes the lingering misconception that current-day SharePoint is no good, simply because of bad experiences with previous versions (read SharePoint 2003). Most of us know that SharePoint has improved with leaps & bounds over the past few years. But if you have to work among, or consult for, those who are still suffering from the destructive symptoms of this disease, : ) here are some great affirmations and other useful phrases to help people feel better about their SharePoint experience:

InfoPath 2010 presentation at Buckeye SPUG: May the FORMS Be With You…

Last nite I gave my InfoPath 2010 talk to the attendees at the Buckeye SharePoint User Group. Despite a nasty snow storm that swept in inconveniently right at the evening rush hour, lots of folks braved the cold and joined me in an engaging and entertaining talk about the untapped power of InfoPath 2010.

The end of the talk included a demo of a form I created call the Dog Lover’s Application. It’s simply a way to demonstrate some standard, and some not-so-standard, features of InfoPath. I used SharePoint 2010’s built-in InfoPath Web Part to embed the form on the homepage of my site. I then asked the audience – “how do you know this isn’t a custom-built web part??” The point I was trying to make is that, with enough clever design, InfoPath forms designers can create some pretty fancy composites that might otherwise normally only be associated with the realm of the all-powerful Developer. : )

My goal was to hopefully make people see the value that InfoPath delivers as another tool in their SharePoint arsenal, and to show that it can be used for more than just the basic form.

The slidedeck can be found below, or on Slideshare::

Top 4 Signs that your Users are embracing SharePoint

{my article published at EndUserSharePoint.com – June 2011}

Have you ever been in an organization, big or small, where SharePoint has been in place for months (or years?), but when you look around, you realize it’s not being used to its full potential? I’m not talking about something big like they’re not using InfoPath for their forms automation, or not using Business Connectivity Services to expose their data through external content types. I’m talking about the organizations who are simply storing old archived documents in a library still named “Shared Documents”, and whose most elaborate web part is the one that shows today’s weather forecast. :) I’m talking about the organization that installed SharePoint, but obviously never heard a good speech about how SharePoint can be used effectively to make their work life more productive.

So let’s say, one day they finally get to hear the speech, and they’re now armed with enough knowledge to get some good end-user SharePoint collaboration going. Other than seeing someone running down the hall with a cowbell screaming “I gotta have more SharePoint, baby!”, how do you know that your users are finally starting to drink the SharePoint kool-aid and use it collaboratively? Well, in true Letterman-style, here are my Top 4 Signs that your Users are embracing SharePoint: