Updating site content type failed infopath
After working for so many years with Share Point, I realized that I might take some things for granted.
I don't question myself so much anymore, when it comes to whether I should create a column, a site column, or a content type - I just do it.
None of them were aware of them, they just created regular columns straight from the list or library.
In this article, my goal is to explain what these columns are and when you should use them.
These don't require any questioning on reusability or architecture, it's an instant consumption. Yes, one of the issues I have found with Share Point is that, sometimes, it's greatest advantage can also be a disadvantage.
The option is right there in front of you, in the ribbon, and will satisfy the immediate need for a column.
When you create a Site Column, you have various additional choices aside from the usual suspects.
As you can see, when you create a Share Point Site Column, it is available to the site and its sub-sites.Advantages: They can be reused by multiple lists and libraries within a site and its subsites.It also helps by centralizing the configuration of the column in one place, which makes it easier to update choices in a choice column, for example, that are used by multiple lists and libraries.However, if you try to interact with another site, it can be very difficult.Unless you have the Standard or Enterprise version of Share Point, with the Content Query Web Part, it will be difficult for you to interact with other sites.