Author Archive

SharePoint 2010 Designer Issues

June 8, 2014 Leave a comment

While it is always good to work with the latest and greatest versions of everything, there are still solutions running on 2010 that need maintenance.

So recently I found myself having to update a SharePoint 2010 solution that was made up of an SPD2010 workflow, a content type and library template. I had to update the content type, workflow and library template with some new and updated columns.

The library template was using a custom Edit form with some of the  content type fields hidden, so I had to update the Edit form to show some new fields. To add a new field to a form you would normally edit the form table to and new rows where needed then select the field from the data source and select as ‘Insert as List Form Field’, unfortunately this option was no available; updating an edited form seems to be a common problem with SPD2010, as the same issue is outlined here.

My solution was as follows:

Select a field in the form where I wanted the new field and insert a new row into the form table, copy an existing control and insert into the new row, using the Common FormField Tasks control select the new control from the Data Field picker



Now Pick ‘List Form Field’ from the Format as  picker



In the Quick Tag Selector bar the new field will be called <SharePoint:FormField#FormField1>


From the Quick Control select Edit Tag…


The Tag code is now displayed with the ID value of  “FormField1


Now check the other fields and find the control with the highest ID value and set the new tag value the be higher in the format “ff<id>{$Pos}”, ensure both references to the ID value are set


If the ID numbering is incorrect a duplicate


Once completed the new control will be available on the form.

Categories: Work

SharePoint 2013, Nintex 2013 Workflow

April 14, 2014 Leave a comment

Recently I have been working with the various Nintex products to create a few demos and prototypes.

Recently while working with a new VM recently I noticed that some of the actions were not performing correctly and the message templates were blank from site to farm level.

None of the normal things seemed to help (IIS Reset, Reboot, Deactivate / Reactivate, Reinstall), until I came across this post on the Nintex forum.

It turned out my VM had the currently withdrawn SharePoint 20103 SP1 applied. As soon I installed the fix normal Nintex service was resumed.

Categories: SharePoint 2013

Opening emails in SharePoint

February 22, 2014 Leave a comment

As part of a recent project we used SharePoint to store emails, both via incoming emails and one of the 3rd party drag and drop tools.


Most users were happy with the solution once we had updated the MIME types to allow emails to be opened rather then downloaded, but some still mentioned they would rather that email opened directly from SharePoint rather than seeing the yellow download bar that Internet Explorer puts up.


A bit of digging around on the internet came up with the solution from this Microsoft KB article

To enable emails to be opened directly from SharePoint the trick is to disable the Internet Explorer download bar for email file types, to do this add the following registry key to your local machine.


then run the assoc command below to get your .msg file extension type (mine is for Office 2013)


Now add that file type as a zero length binary value to the key created above.


Emails will open directly from SharePoint.

SharePoint 2013 on Windows Server 2012

January 28, 2014 Leave a comment

There are quite a few articles about installing SharePoint 2013 on Windows Server 2012 around, but I thought I would share a real world experience.

Pretty much the first thing that the SharePoint 2013 Deployment Tool does during an install is try to add the Application and Web Server roles to Windows Server.


If your Windows 2012 Server has internet access then you should have no problems, but if your server does not have internet access then you will need a copy of the Windows server ISO and these instructions below as the server roles are now on demand with Windows Server 2012.

A couple of points to note, firstly there is a typo in the instructions for the Offline method.

This instruction

Add-WindowsFeature NET-WCF-HTTP-Activation45,NET-WCF-TCP-Activation45,NET-WCF-Pipe-Activation45-Source D:\Sources\sxs

should read

Add-WindowsFeature NET-WCF-HTTP-Activation45,NET-WCF-TCP-Activation45,NET-WCF-Pipe-Activation45 -Source D:\Sources\sxs

note the space before the –Source switch

secondly, the KB article states

Note Be aware that you can also copy the files locally or specify a UNC path where the installation files are stored.


We found that having the files copied locally or the ISO file mounted locally worked fine, but trying to run over a UNC path worked for the 1st set of features but failed for the 2nd set with a PowerShell error, as soon as we mounted the ISO locally the 2nd set worked fine.

If your PowerShell works as it should, you will get a result as below.


Categories: Work

SharePoint 2010 Workflow Issues

January 10, 2014 Leave a comment

I was recently asked to help out a client who was having problems with standard Out Of the Box Approval workflow.



We checked the Farm and isolated the issue to one specific site collection, all other site collections were fine.

To resolve this we opened the site collection in SPD, open the All files section drilled into the _catalogs/wfpub folder, the folder for the Approval workflow was present but for some reason the wfconfig.xml file had been modified from the site definition (Shown by blue I symbol), once this file had been reset to the site definition workflows were working again.

Categories: SharePoint 2010 Tags:

Search in SharePoint 2013..increased functionality makes it simple!

November 20, 2013 Leave a comment

Good article about search refiner improvement’s in SharePoint 2013


One of the search features introduced with SharePoint 2010 was the concept of search refiners and this really gave power to the users to filter and work with search results. This capability was surfaced as the Refiner Panel in the search results pages and was driven by metadata values assigned to the content. The benefit of this was that users can work with large results sets and narrow down the search results based on meaningful business criteria.

Out of the box, the standard refiners were based on metadata generated directly by SharePoint and users were not able to configure these to their liking. The types of refiners that would typically be made available include Result Type (the type of file such as a Microsoft Word or Microsoft Excel document), the Author of the piece of the document, the Modified data etc.

pic 1pic 2

Whilst it was quite possible to add new refiners…

View original post 531 more words

Categories: Work

SQL 2012 Quick pointers for SharePoint 2013 – SharePoint Community

November 20, 2013 Leave a comment

Some good quick tips from SharePoint community site

Categories: Work Tags:
%d bloggers like this: