If you have 100 sub sites, and all site columns are created at the top, you will quickly find yourself overwhelmed with columns that are not needed in most sites.

updating site content type failed infopath-34updating site content type failed infopath-34updating site content type failed infopath-85

In some cases, it can be useful to create a Lookup Site Column, so that the actual lookup will also be available in sub sites.

Take the diagram above for instance: if Site Column A was a lookup column to a list of customers available only in the Top Site, then all sub sites would have the Site Column A with the lookup to the customers list in the top site.

We create a table and, as we add columns to this table (list/library), we are asking whomever is entering information in it to specify certain details we call "Metadata".

However, the columns we have in a list or library can be created or added in multiple ways. This is probably the most popular type of column created.

Share Point also offers the possibility of creating Site Columns. They're columns we create in a Share Point site, and are available to its subsites.

As you can see, when you create a Share Point Site Column, it is available to the site and its sub-sites.

My mistake is in assuming that Power Users who are using Share Point every day, or migrating to a new version they might not know, already know which to create.

I did a one day power user training for a customer of mine recently, and saw their jaw drop when I told them what we could do with site columns only.

This was simply due to human error, after repeating the same action so many times.

Others realized that it was just too long to update the column with new configuration, because they had to go to each library in the site, one by one, to edit them.

However, if you try to interact with another site, it can be very difficult.