Validating title/name columns to enforce capitalization

From a question on my course, we had a look on how to validate title fields of a SharePoint list and enforce that names are capitalized.

First, we added some proof columns for testing purposes.

We get the first letter using the formula:

=LEFT([Title],1)

We also want to see what the upper-case version looks like so that we can compare the two.

=UPPER(LEFT([Title],1))

However, validation does not take capitalization into account. Therefore, we cast the letters into ASCII code format using:

=CODE(UPPER(LEFT([Title],1)))

We can now write a validation expression on the title column as:

=CODE(UPPER(LEFT(Title,1)))=CODE(LEFT(Title,1))

For more info, see this good series of column validation posts: http://sharepointsolutions.blogspot.se/2012/03/series-of-posts-on-column-validation-in.html

Great new CloudShare feature: Persistent DNS with vanity URL and CNAME

CloudShare virtual machines (of which I manage about 35 of for our company) can now have persistent DNS entries for external addresses. This is great for creating a permanent RDP connection link and using external links for testing purposes.

You can also personalize these URLs using vanity URLs from the Account Settings screen. Here’s my updated settings.

Even better, you can deploy test and UAT rigs using CNAME aliases, so I could apply the web URL sptest.lekman.com.

For more info: https://support.cloudshare.com/entries/23712067-Persistent-DNS

Updated release of AutoSPInstaller solves slipstream issues

An important update to AutoSPInstaller is now available that allows the installation of cumulative updates without the need for slipstreaming.

There is currently an open issue where slipstreaming of cumulative updates for SharePoint 2010 from August 2012 and onwards will fail. If you are planning on installing this CU or later, then you must apply this manually afterwards and The issue *should* be fixed with the release of SP2.

With the latest release of AutoSPInstaller, you can now apply cumulative updates without slipstreaming.

More info:

- New function: InstallCumulativeUpdates - enables Public and Cumulative Updates to be installed in sequence and without the need for slipstreaming. Also avoids issues with slipstreaming introduced by recent updates (Aug 2012 CU and beyond for SP2010, and April 2013 CU for SP2013).

http://autospinstaller.codeplex.com/SourceControl/changeset/100318