Email Enabled Calculated Fields

10 05 2017

I am back! Today I am going to show you how to use calculated fields to form an email address and a clickable link to send to that email address you just created.
The ask was to create a custom list that had the following fields:
Cost Code
Location City
This information just happened to be avaialable in another SQL database, so rather than populate it it manually, I decided to go BCS all over that sucker. BUt, that’s not what we will talk about today.
Once that information is safely in SharePoint via external contentype, I used 2 calculated columns to get the email and the mailto link.
The first calculated column was used to concatenate the cost center and location to form the much needed address. So if you are following at home create 2 calculated columns.
The first colum will take Cost Code and Location city, mash them together and spit out an email address the address in the following format
Since i have no column named store, i will just hard code it in. Here is the email formula:
=CONCATENATE(“STORE”,[Cost Center],Location_City,”@mystore.COM”)

Now, to make it a clickable mailto link, i really had to mess with the html. For your second calc column add this formula:

You guessed it, EMAILCALC is the name of the first calc column.
that’s it.
Love me.


SharePoint Logos: One logo to rule them all.

13 05 2015

I have been racking my brain trying to figure out a way to force all sites in my SharePoint farm to use the same logo. Obviously I should have stapled it to my master page before pushign it out, but as usual I suck.
So i decided to break out the old PowerShell machina and take a crack at it.
I found a bunch of sites that showed how to do this for all SUBSITES in a Site Collection, but not all Site Collections and subsites.
Here is what I came up. Hope it works for you guys.
This code is as is and I don’t take any responsibility for screwing up your farm.

$sitelogo=”SPSITE where your logo resides usually _layouts/site assets/”


$Sites=Get-SPWebApplication $Site|Get-SPSite -Limit All |Get-SPWeb -Limit All|Select URL

$Sites|ForEach-Object {


$CurrentSiteObject=new-object Microsoft.SharePoint.SPSite($CurrentSite)

foreach($web in $CurrentSiteObject.Allwebs) {




Happy SharePointing!


InfoPath is back from the dead…sort of.

10 02 2015

As you may or may not know, InfoPath has been the subject of much speculation in the SharePoint community, with Microsoft saying that they will be killing it off, then changing its mind about it. Well they officially changed their mind about, at least for the next version.
Microsoft updated it’s blog post with the following:

“As part of the update shared around the Evolution of SharePoint and the next SharePoint Server on-premises release, we are also updating the timelines for removal of InfoPath Forms Services components of SharePoint and SharePoint Online. Specifically, InfoPath Forms Services will be included in the next on-premises release of SharePoint Server 2016, as well as being fully supported in Office 365 until further notice. Customers will be able to confidently migrate to SharePoint Server 2016 knowing that their InfoPath forms will continue to work in their on-premises environments, as well as in Office 365.
The InfoPath 2013 application remains the last version to be released and will work with SharePoint Server 2016.”
Here is the link

So, in honor of InfoPath’s Ali like return to the ring, i say unto you, InfoPath on my people. It will be ok.


View HTML pages in SharePoint Online.

23 07 2014

Did someone in your organization save an entire website in a document library?
Did they complain they couldn’t open the start.html page?
Do you have users that want to view html pages inside SharePoint online?
If you answered yes to any of these questions (i am aware of the irony of this post), then I have a solution for you!
Simply open your html files in your library using explorer view and change the extension from HTML to ASPX. It even works with Flash content.
Yup, its that easy (and confusing at the same time, but for other reasons).


Sp2013 AppDomain – YOu have to do what?

20 03 2013

So after all this time, some people are still having issues with the app domain. I came across this little golden nugget of info after installing an app domain with a host header web application:

*Important – please note that if you are using Host Headers for your Web Application then you will need to create a new Web Application on port 80 that doesn’t use Host Headers. This Web App must have a root site collection which can be of any template. If you don’t do this then when you try to click on an App you will be met with a 404 error. This is because SharePoint uses the site running on Port 80 to resolve the app url, this must be a SharePoint site so the Default Web Site won’t work. Once you have created the Web Application and blank Site Collection do an IISRESET just to be sure. For more details on this check out Mirjam’s post here.

What is up with that?

SharePoint 2013 and Office WebApps: The Binding Dance Off!

3 02 2013

After installing SharePoint 2013 and configuring it with Workflows and app domains, the last piece of the puzzle is to install Office web apps. Pretty simple really if you follow these steps from SOWMYANCS :Install, Configure & Monitor Office Web Apps 2013 for SP 2013

However, no matter what i tried, i couldn’t get office web apps to work quite right. It wanted to launch in the window, but it would get stuck there for 5 minutes then tell me the office webapp service was busy or this dandy error:

Word Document: “Sorry, Word Web App can’t open this document because the service is busy.  Please try again later.”

Word Document : “Sorry, there was a problem and we can’t open this document. If this happens again, try opening the document in Microsoft Word.”

I scoured the internet and nothing. Then it dawns on me. I had demoted this server from being a Domain Controller. Somewhere in the instructions i had read that OWA server cannot be a domain controller. But it doesn’t say it should have NEVER been one either.

I went ahead and installed a fresh copy of Windows Server 2012 with all the updates.

I went back to my SharePoint WFE and ran:

Remove-SPWOPIBinding –All:$true

I re ran the steps from the above article

New-OfficeWebAppsFarm –InternalURL "http://servername" -ExternalURL "" –AllowHttp -EditingEnabled

Turns out that SharePoint remembers all your SPWPIzones from before. So if you wan’t external access you need to run this command to make sure you know what zone you are in:


Then make sure you set your spopizone to external by running this command:

Set-SPWOPIZone –zone “external-https”

Now it works.
Moral of the story, don’t reuse domain controllers, even if you have demoted them. They will always be bitter you demoted them.