You two are the best! Immediately running into a concern, hoped you might have some advice? My child content types inherent a choice column from the parent content type. Each child content type should have a different default value for the choice column but should be able to select a different choice value when needed. 1. If I inherent the column from parent, it seems like the option for default value is not allowed in the children. 2. The workaround might be to not inherit the column, but then if I were to switch content types for an existing doc in my document library it erases the metadata as if it's a totally different column, but still shows in the list view. 3. In the list view I see all the files metadata under one column, but in the library settings you see several with the same name (one column of for each content type)... Is there some merging of columns thing that needs to happen?
how to deal with sensitivity labels with new documents created on the same doc. library ? assuming new documents won't have Content Types as in "project files" based on the demo.
It seems to me that whilst this is a really handy thing to have, if I have 100s of sites to roll this out to - I would still need to either instruct end users on how to manage view settings or create a default view for each site. Is there a way to push out a default view based on a content type across multiple sites? Unles I'm missing something!
@@WonderLaura is it possible to edit it directly in the word file? Because I tried to put quick part into the template but it is not editable, I can change it only from sharepoint item settings not directly "inside" document.
I would love to start with an example of someone using it in the real world and then move into how they built it. instead of saying 'you could do this, or this, or this, but then do it differently this way or this way...." just too confusing
The best Tuto about Content Type on the net. Thank you both of you 🙂
Wow thanks!!😊
You two are the best!
Immediately running into a concern, hoped you might have some advice?
My child content types inherent a choice column from the parent content type.
Each child content type should have a different default value for the choice column but should be able to select a different choice value when needed.
1. If I inherent the column from parent, it seems like the option for default value is not allowed in the children.
2. The workaround might be to not inherit the column, but then if I were to switch content types for an existing doc in my document library it erases the metadata as if it's a totally different column, but still shows in the list view.
3. In the list view I see all the files metadata under one column, but in the library settings you see several with the same name (one column of for each content type)...
Is there some merging of columns thing that needs to happen?
Should site collection admins be allowed access to the SharePoint Admin pages and the ability to create new multi-site content types?
It’s up to you for your org
Is there a way to share SharePoint content types and term store with sites that are associated with a SharePoint hub site?
Ooh that would be nice, but those 2 features don’t recognize each other in that way.
Is it possible to see the new columns created in File Explorer after syncing with One Drive?
SharePoint and OneDrive columns aren’t going to appear in Windows explorer.
how to deal with sensitivity labels with new documents created on the same doc. library ? assuming new documents won't have Content Types as in "project files" based on the demo.
What do you mean “deal with”? What’s the goal?
@@WonderLaura what would you recommend as best practices for sensitivity labels with new documents created on the same doc. library
It seems to me that whilst this is a really handy thing to have, if I have 100s of sites to roll this out to - I would still need to either instruct end users on how to manage view settings or create a default view for each site. Is there a way to push out a default view based on a content type across multiple sites? Unles I'm missing something!
With custom site templates which used to be called site designs, that is possible. Not easy, it involves scripting and PowerShell.
How do I get my custom site columns into the template as quickparts?
Here’s a post I wrote about quick parts wonderlaura.com/2019/01/09/microsoft-flow-quick-parts/
@@WonderLaura Thanks. I'm sure Microsoft could make this easier.
@@WonderLaura is it possible to edit it directly in the word file? Because I tried to put quick part into the template but it is not editable, I can change it only from sharepoint item settings not directly "inside" document.
Should content types pulled via quick parts into documents show in the web app?
Yes.
I would love to start with an example of someone using it in the real world and then move into how they built it. instead of saying 'you could do this, or this, or this, but then do it differently this way or this way...." just too confusing