The link to the Project is
This edition of the CodePlex Corner turns its attention to a product called the SharePoint List Field Manager.  At the time of its launch, it was created as a value-add product for CorasWorks customers and has been developed by their VP of Technology, Adam Macaulay.   In May 2010 the company decided to release the product into the SharePoint community via CodePlex.  The List Field Manager currently comes in three flavours: -

  • SharePoint 2007
  • SharePoint 2010
  • SharePoint 2010 Sandbox

The List Field Manager does one thing but it does it very well.  It allows you to set the Boolean properties on any column within a SharePoint list or library.  In plain English, it partially addresses one of the perceived gaps of SharePoint.  That’s the lack of granular permissions insofar as column/view level security is concerned.  Once this product is installed and activated it allows you to configure, on a field by field basis, the following settings: -

  • Hidden: This sets whether a field can be displayed in the list
  • Read Only: This controls whether a field can be modified by the users
  • Show in Display Form: This controls if a field is displayed in the DisplayForm.aspx
  • Show in Edit Form: This controls whether a field is displayed in the EditForm.aspx
  • Show in New Form: This controls whether a field is displayed in the NewForm.aspx
  • Show in List Settings: This controls whether a field can be modified via List Settings
  • Show in Views: This controls if a field is visible within List Views
  • Allow Deletion: This controls whether a field can be deleted or not
  • Show in Version History: This controls whether a field is displayed within an items Version History

These properties can also be accessed and changed in PowerShell and the SharePoint Manager, as seen here.  Their only configurable options (in true Boolean style) are True or False.  The List Field Manager simply provides a more accessible interface for accessing them.

More information on the Field Properties is available on MSDN on this link.
Let’s think about some of those options for a moment and the power that they provide.  What other major SharePoint technology gives us the alternative to work with columns in such a way?  InfoPath forms.  Whilst the List Field Manager isn’t (and was never intended as) as a substitution for InfoPath, it does provide a great “no cost” alternative.  This means that you can use things like calculated columns for various effects (such as calendar colour coding) and hide them from various .aspx forms and views.  This allows either the Foundation or Standard versions of SharePoint to be extended and manipulated in simple but powerful ways.
Post installation the List Field Manager is available in the Web Part Gallery and allows you to select any list from a provided URL once it’s been activated.  You can then select the field and set as appropriate.  Compare some of the options below to the earlier screenshot from SharePoint Manager and you’ll see the same properties.

The product was also tested against the forms generated with External Content Types.   The AdventureWorks Community samples were used to build an external content type and an external list from the customers table.  All the typical CRUD operations were defined with the end form looked like this.

With a few grammatical tweaks to the labels this would make a workable list but that Demographics field really doesn’t serve any purpose being surfaced within SharePoint.  The List Field Manager picked it up just fine but wasn’t able to tap into any of the properties that we can manipulate with SharePoint Lists.  This was taken as confirmation that the List Field Manager can only be utilised against internal content types.

Link to product review

The link to the SharePointReviews Product category is to be located under Content Management à Lists and Libraries on the following URL:

“End User – Developer” scale

Working on the basis that an Administrator will have installed this web part in the appropriate fashion; the List Field Manager is fairly straightforward to use. This product presents an acceptable alternative to InfoPath form development.  On that basis, the product can be rated at Power User level.  Administrators &  Developers shouldn’t have that many problems with the List Field Manager in return for the functionality it provides them.

Potential pitfalls / problems

The only potential problems or areas of concern for this product are: -

  • Limitations of Sandbox Deployment: Sandbox 2010 Deployment doesn’t allow cross site list management (this is referenced in the CodePlex documentation however)
  • Settings not added to Site Settings: As this is a web part, not a link in the site settings, an administrator might potentially forget where this web part has been deployed.  In a potential workaround, you could possibly set up a dummy view page called Admin, delete the list view and add this web part to it
  • Hidden vs. Read Only Properties: The differences between the Hidden & Ready Only properties are confusing.  Read-Only won’t surface a column but then lock it for editing, it removes it from the form.
  • Internal Content Types Only: Doesn’t work on external content types

Conclude and add any relevant links

In closing out the article, the List Field Manager is clearly a great tool.  It provides an awful lot of utility and is something that can conceivably be farmed out to well-trained or experienced users which removes a small dependence on IT or the SharePoint professionals. 
The links below were used in the article write-up: -