Forum Discussion
How to Properly Delete Custom Columns in SharePoint
SharePoint custom columns have been around for quite some time, but I’m finding that there’s still some confusion on how the various types are used, and more importantly how can you delete them. In ...
While there is a lot of good information in this article, it fails to mention a common problem that occurs when a Site column is created in a lower level of a site collection, the column is not available to the parent sites nor in the sibling sites. This can lead to a tremendous amount of confusion if another column is added to the top of the collection.
I strongly recommending creating all site columns at the root of the site collection
I strongly recommending creating all site columns at the root of the site collection
- Good advise, and one should create them in the content type hub first, correct?
Or no?It really depends on the scope of usage and your need to control deployment. Anything in the CT hub will show up "everywhere" and in SPO you don't have any control over when the changes in the CT hub get pushed out.
Just like almost everything in SP, the "best practice" has caveats and exceptions :)
Well said, Dean_Gross. I'm always on the fence when it comes to using the CTH. There are some clear benefits but also limitations as you've stated.
- You are so right, Dean - I learned this the hard way! Plus, for me it's just easier to manage. However, if you have a site admin who wants to use site columns but doesn't have site collection admin rights, you'll have to do some permission tweaking to allow them to create them at the root level. Or you can do it yourself :)
Dean_Gross, you're absolutely right. Creating site columns in subsites is a common poor practice. My goal with this short article was to focus on issues commonly faced when deleting existing columns. Appreciate your feedback! :smileyhappy:
