The Baretta

----------------------------------------------------------------------------------------- This post is related to a larger group of posts called  Migrate SharePoint to Office 365 - Planning & Steps ----------------------------------------------------------------------------------------- I've gone with a Publishing Site Collection so that I can use the 'Alternate CSS URL' in Site Settings > Master Page. First off, thanks to the following websites which helped get me started: http://blog.sharepointexperience.com/2015/02/sptechcon-austin-february-2015/#more-2766 http://blog.sharepointexperience.com/2015/01/to-brand-or-not-to-brand/ Here's what the end result will look like (if you have the same fonts): Now for the CSS... /* Design By : Brett Randall */ /*     Design Colours: Greens/Greys/Blues */ /*     Last Modified : 28/02/2017 */ /*     Description: CSS to rebrand SharePoint Online Publishing Site Collection that is...

Just a quick one after some deep thought. Thoughts on the Future: If you have to create an InfoPath Form, you should be creating it as a List Form (if possible), not a Form Library.  The reason for this is ease of upgrade now that InfoPath will not be upgraded/supported by Microsoft. If you have to create a Form Library (because you form requires repeating tables/sections): I’ve decided that InfoPath forms should NOT be published as Content Types.  The only time it would be considered OK is if the form is very generic and is being used on multiple sites.  E.g. a Help Form which could be used by multiple departments without any modification. The main issue when publishing as a Content Type is that every field you promote to be visible in SharePoint has to be created as a Site Column. This means that even for a small form, for instance, a Personnel Access Form, you’d have to create Site Columns for fields like: Room Number or Access Hours, which would only ever be ...

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 ...

Earlier today I wanted to modify the address of the 'Pages' library on a SharePoint 2010 site.  The reason behind this was to make the naming of the folders more user friendly for our developers who would be deploying reports there. There wasn't a way to do it from the standard GUI, so I decided to modify it in SharePoint Designer (Hey, if SP Designer allows you to do it via GUI, it's safe right? ... right!?). Bad move, as there's some behind the scenes magic that must be hard-coded to the Pages URL, which breaks the Navigation Settings page (this one: http://[sitecollection]/_layouts/AreaNavigationSettings.aspx). 'An Unknown Error has Occurred' - Great.. I'm sure there would be a way around it, but for the sake of saving a few hours of investigation, don't change the name of your Pages Library! Ciao ciao!