Forum Discussion
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 idea as you can't reuse them across multiple lists. At least I've been training my customers to create content types/fields at the site collection level.
If it was easy to add site collection columns to my view similar to the current add new column functionality then that would be great. But for site columns I still need to go to the list settings.
3 Replies
Hi Pieter - I also council people that site columns are the preferred type of column so I would also like this discussion to be rich. Here is why site columns are superior: 1) They influence search relevance more than list columns because they are made into managed properties. 2) When created in the gallery in the top level site of the site collection, they can be added to any list in the site collection.
Here is why list columns are superior: 1) They are easier for users to add.
Greg
- 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).
