InfoPath, Content Types, Site Columns & The Future
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 ...