Helpful tip for anyone stuck at 57:00! 🛠 If your content type isn't syndicating after publishing from the central hub, check your hub site level settings first (instead of individual site settings). When I did this, syndication happened almost instantly. Saved me a lot of troubleshooting time! Hope this helps others 👍
Gotta say, this did not work as expected. When I created your "Project A" it did not show up in my list of items on the left hand side per 27:33. When I tried to create a project document it created a new ODT doc in Word (on my machine) and then when I saved it as a Project A document, it saved it in OneDrive rather than the SharePoint library I expected it to be in. I have used SharePoint for many years, and tried to avoid the idea of the Document Set scenarios, and now I know why. This is the most confusing thing I've ever experienced in SP and will avoid it like the plague going forward. It's wierd that your demostration clearly had one set of outcomes and mine had a very different one. MSFT needs to clean this up or kill it.
@@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.
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.
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?
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!
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
Helpful tip for anyone stuck at 57:00! 🛠 If your content type isn't syndicating after publishing from the central hub, check your hub site level settings first (instead of individual site settings). When I did this, syndication happened almost instantly. Saved me a lot of troubleshooting time! Hope this helps others 👍
The best Tuto about Content Type on the net. Thank you both of you 🙂
Wow thanks!!😊
Gotta say, this did not work as expected. When I created your "Project A" it did not show up in my list of items on the left hand side per 27:33. When I tried to create a project document it created a new ODT doc in Word (on my machine) and then when I saved it as a Project A document, it saved it in OneDrive rather than the SharePoint library I expected it to be in. I have used SharePoint for many years, and tried to avoid the idea of the Document Set scenarios, and now I know why. This is the most confusing thing I've ever experienced in SP and will avoid it like the plague going forward. It's wierd that your demostration clearly had one set of outcomes and mine had a very different one. MSFT needs to clean this up or kill it.
This video was recorded almost 2 years ago, so it's possible that Microsoft made significant changes since then.
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.
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.
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
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?
You'd just have to not put a default value in there at all and do the default value at the library level.
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.
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.
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
Ill do that next time