The Baretta

Sorry, something went wrong Field type [FieldName]  is not installed properly. Go to the list settings page to delete this field.   This is caused when a FieldType has been created usually via a custom solution (WSP), and has been used somewhere, then uninstalled while still being used somewhere on the Site Collection.  This error message is similar on all versions of SharePoint 2007/2010/2013. Usually you will have one or more Site Columns that are using the FieldType, and possibly one or more Content Types that are using that Site Column, and then most likely one or more Lists/Librarires using the Site Columns or Site Content Types. If you want to remove the Field Type Completely, steps to resolve are as follows: Try to delete the Site Column or Content Type from every list it is being used on.  If you can't delete the Content Type from the list, you will have to delete the list. Delete the Content Types using the Site Column (Site Actions >...

Have you recently upgraded to SharePoint 2013 but can't seem to open excel or word docs inside a Document Library? Are you getting a URL that starts something like this? ms-word:nft|u|  ms-excel:ofv|u| Chances are it's because you have both Office 2010 installed on your computer as well as either the full Office 2013 suite or any single Office 2013 product (Here's looking at you SharePoint Designer 2013!!!). The reason for this is related to the new Microsoft SharePoint Foundation Support feature that gets updated when you install an Office 2013 product, in turn updating a few pointers to look at the Office15 Hive folder. Others have solved this issue before me, but to save you having to read lots of comments, the solution is to install Office 2010 SP2 . Here's some links to a few blogs that helped me realise the cause and find the solution. http://blogs.technet.com/b/projectsupport/archive/2013/04/04/sharepoint-2013-problems-opening-documents-with-of...

If you're like me and needed to have quite a few tiles in your Promoted Links Web Part, this should come in handy. I've seen options to install custom solutions, and i've seen options to add a javascript file to the web part to force it to go to a new line. Custom solutions?  meh. Seperate 76kb javascript file?  meh. Use what you've been given my friends; and make it simple for your siblings to see how it works. It's not entirely a simple solution, but when completed I think it is the most elegant/clean solution.  Create two Promoted Links Web Parts underneath each other and use two separate Tile Views to display everything you need.  The only way I could find to create another Tile view was to use SharePoint Designer. Navigate to list in SharePoint Designer 2013 Create new view Copy CAML Query from original Tile View to new Tile view.  Copy This Bit (Make sure you keep the old view name, display name, url): <XmlDefinition><View Name=...

The other solutions I've found regarding this involve javascript/jquery.  Was unable to find any CSS that resolves the issue nicely. This seems to have resolved the issue for me so far without compromising any other areas of the site.  It hides the initial link and then goes back to displaying the rest of the navigation as per normal: <style type="text/css"> .ms-core-listMenu-horizontalBox li.static > a{ display: none !important; } .ms-core-listMenu-horizontalBox li.static > ul a{ display: block !important; } </style> Liked this post?  Check out my other posts regarding Global Navigation here: What Should Be Allowed To Go I n Global Navigation? The Best OOTB Cross-Site Navigation Solution for SharePoint 2013/2016/Online

Deploying an InfoPath form Once you have developed your InfoPath form, most likely you will need to deploy/publish it to SharePoint so that the information can be stored and reported on.  There are different methods for deployment, which are also dependent on whether you are publishing a fresh form, or updating an old form. Two methods of Deploying/Publishing Forms When it comes time to deploy your form to SharePoint, there are two different methods with reasons for and against why and when you would use each.  You can publish the form as a Form Library, or as a SharePoint Content Type. Deployment Method 1:  As a Form Library When you publish a form as a Form Library, it will create the library on the SharePoint Site of your choosing, and a copy of the form template can be found here:  http://rootsite/formlibrary/forms/template.xsn Use this method when you only require one library for the forms and the forms do not get consumed by BizTalk for some ...

G'day,        Just a quick note to say if you haven't heard of it already, then you should check out this solution on CodePlex that is absolutely awesome:  http://responsivesharepoint.codeplex.com/ What it contains: - Responsive resizeable Master Pages & Page Layouts for SharePoint 2013 that work with Twitter's Bootstrap CSS. - Responsive resizeable Master Pages & Pages Layouts for SharePoint 2013 that work with Zurb's Foundation CSS. I've tried both briefly but so far prefer the Bootstrap version for the font types and colours.  Although I most of us will be making modifications to suit the clients that we are working with, they are a great starting point to Responsive Design for SharePoint that have been designed very well. If you don't have time to build your own solution from scratch, this is the perfect starting point to build on top of.  Congratulations and thank you to all who have worked on the project so far! More...