5. June 2015 11:22
When migrating content I need fine grained control over which containers content goes into or retrofit metadata not originally available. I find using Excel and powershell together to be a very powerful and flexible way forward. [More]
9. April 2014 09:47
A quick example of how to create multiple Document Sets in SharePoint driven by a CSV file for the names and properties. Changing a couple of lines would allow this script to create simple Folders instead (but Document Sets are better!). [More]
10. January 2014 10:38
For a particular Form Library I was interested in making it difficult to do too much with the Forms except add them. I employed a range of measures, one of which was to hide the ribbon buttons for Sharing or opening with Explorer View.
This can be done by creating a customAction and deploying it to your site. Some of this is documented elsewhere, but I noticed that there were no examples showing multiple buttons hiding - the examples showed a single instance. Also the examples always showed a "RegistrationId" of 101, without explaining that this targeted Document Libraries. To target Form Libraries I had to dig up the fact that "RegistrationId" of Form Libraries is 115.
The xml looks like this;
To get this into your site, create an empty SharePoint project in Visual Studio. A sandboxed solution is fine. Add a feature to the project, and paste the above XML into the Elements.xml file. Smallest scope for the feature is Web.
Build and add the WSP to your Solution Gallery via Site Collection Settings. When activated, and the Feature activated in a given Web, it will hide the named buttons in all Form Libraries in the current SPWeb.
Here's a list of other elements you could hide using the above method; http://msdn.microsoft.com/en-us/library/ee537543(v=office.14).aspx
Mike Smith kindly documented the many Registration IDs for different libraries here; http://techtrainingnotes.blogspot.ch/2008/01/sharepoint-registrationid-list-template.html
3. December 2013 06:02
Today I'm reviewing harmon.ie for Outlook at the behest of Harmon.ie .This is a tool I use daily at work and train other users on, so let the write-up begin! :) [More]
21. November 2013 08:28
Over the past year or so I've spoken to some SharePoint customers who have been confused by the SharePoint message coming out of Redmond. Microsoft, in their enthusiasm to promote Office 365 have not really assured customers on the future of SharePoint On-premises. There's been a real lack of any clear message about the product and no roadmap was published. Anecdotally this has led to some nervousness amongst customers, and the question has been asked 'Is On-premises SharePoint dead?'. Asking such a question might sound melodramatic, but believe me - silence from Redmond on any technology often means it's doomed.
Don't get me wrong, I believe there are many positives to Office 365 and Cloud in general. I see Office 365 as a great way to make SharePoint available to smaller organizations to whom On-Prem would not be cost effective. However the shift isn't going to happen en masse quite yet. Just look at Gartner’s comments that for example only 8% of office system users employ any sort of cloud based email at all; here In my part of the world, Switzerland, I find many of the large Enterprises have a 'no cloud' rule. Until certain issues to do with guaranteed up time, connectivity, and state snooping are resolved, that is not going to change here. [Update 4th December 2013 Microsoft have issued a very welcome communication on Government Snooping here ]
SharePoint On-Premises is still how the vast majority of customers use SharePoint and it's still a major cash cow for Microsoft.
I'm preparing for the day I might have to move our farm to Cloud (I'll detail how in future blog posts) but I don't expect it to happen for at least five to ten years if it ever does. Many other customers may take the same view.
With this in mind I'm relieved today to see an official post on the MS Office Blog. Not only does it herald the coming release of Service Pack 1 for SharePoint 2013, but it also states here
" we look forward we'll continue to deliver rapid innovation through our Office 365 service as well as continued future on-premises versions of SharePoint on our traditional release cadence of 2-3 years."
This is gold. We'll continue to get rapid innovations and releases from Office 365, for those that want it. However On-Premises is still alive and kicking, and as organizations we still have the stability of not making major changes to the platform outside of the current 2-3 year cycle we know and love. Big business has the stability of the platform it needs. A message I'd have liked to see at least a year ago, but welcome now nonetheless.
31. July 2013 20:48
Combined Knowledge have just posted the photos from this years SharePoint Evolution Conference. I was a speaker so I made it into some of them, shown here. If you weren't there, make sure you make it to the next one! :) [More]
24. July 2013 23:05
Recently saw a request to get rid of the delete option on a view item form, but retain the ability to switch into edit mode. As both options were on the ribbon and couldn't be removed independently I came up with a hack. Here is one idea for faking buttons on your InfoPath List Forms so that functionality you couldn't otherwise have can be attained! [More]
20. June 2013 20:57
There are two options to hide the ribbon on InfoPath List Forms. One easy, one a little complicated, but there's a good reason to choose the complicated one (if you need it!). [More]
19. May 2013 13:21
When searching for Certification info for SharePoint 2013 the only game in town seems to be the MCSE. This is extremely weighted towards server setup and configuration, and requires certification in Windows Server 2012 before getting anywhere near SharePoint. The Developer certs such as MCPD are to be retired so things were looking bad for Developer Certification. Thankfully, information about a Developer Certification Path are now surfacing. [More]
10. April 2013 14:43
How to remove the ribbon and add your own buttons to a SharePoint InfoPath List Form isn't obvious. Here we see how it's done. [More]