Forum Discussion
Aug 15, 2016
Site collection columns vs list columns
In the new look lists/libraries it's been made easy to create new list columns and then save the view with the additonal columns. Are list columns a good idea? I thought that it isn't a good i...
Vadivelu_Balusamy
Aug 15, 2016Iron Contributor
Pieter Veenstra : Thanks for bring this topic. All the columns were created based on the requirements. Since from the beginning, the design of site column and list/library column is reusable based on the customization what we going to do.
Might be your organization having the idea to create a content types/fields at the site collection level for each list/library. But all the Power users always using the list/library fields based on their day to day life business. In fact, if we bring the site collection columns in my view, we need to have the control to change the name of the column. It is not advisable and not good from normal activity which we are seeing from beginning in all versions (MOSS 2007, SP2010, SP2013, SPO).
Might be your organization having the idea to create a content types/fields at the site collection level for each list/library. But all the Power users always using the list/library fields based on their day to day life business. In fact, if we bring the site collection columns in my view, we need to have the control to change the name of the column. It is not advisable and not good from normal activity which we are seeing from beginning in all versions (MOSS 2007, SP2010, SP2013, SPO).