Hello, if you've seen my questions, you know I am at a very basic level of administration and basically just the ECM side. We have custom content hubs that are published from the hub to 3 site collections. Right now, all content types are 'Read
Only' which eliminates anyone making changes to our column fields without knowing or working around our governance.
We do not use designer. It is turned off.
The problem we have is that users are encouraged to use columns and custom views to oranize and filter their libraries. BUT, if the content type is read only, the library-level custom columns are not visable during the upload of a file and populated
our required metadata. The columns can be seen with views but are not easy to populate. Going to a spreadsheet view is not easy to navigate or populate.
We want to 'turn off' the read only so that content types can have the custom columns added. This allows a user to populate metadata field that are required by our goverenance plan as well as custom fields they have added to their library. This has
been testing in our TEST environment but content types were never read only in that environment.
Question- if we changed the setting to content types in PRODUCTION, what technical issues will this cause? Are there other implications I don't know that will cause problems with publishing from the Hub?
We use the content hub because its ease to push down changes to the site collections so I don't want to change this setting at the local site collection leven and then republish from the hub later and have the hub override our local changes.
Has anyone experienced this or know changed content types to NOT ready only in the content hub will cause other problems?