Best practice for provisioning Content Types on Modern Sites
Hi, I'm looking for the best way to work with content types on modern sites. Currently the Content Type Hub (cth) is used for our classic sites and can't be deactivated. We started a new project to provision modern sites wit PnP Provisioning Engine. If a modern site is created, the content types from the content type hub are not available for some time. Adding content types from the cth to list or libraries makes this impossible for the provisioning engine. I see a few options 1. Create a modern site that won't get the content types from the cth and add create content types manual on the template site collection. I don't see how we can technically make this possible... 2. Reuse the provisioned content types from the content type hub in the template site This might give a conflict when the content types are provisioned by the PnP Prov Engine and not by the content type hub, not sure if this is a valid argument. 3. Create (next to the one from the cth) new content types in the template site. there will be an overlap of content types... This approach makes it more difficult for reporting or search queries. I'm looking forward to your ideas or best practices. Cheers BerndWhere is the root site to create Site Columns and Content Types for the /Sites Subsites?
I am attempting to create some standardized Site Columns and Content Types that would be accessible in any of the Sites that full under the /Sites tier of the template (Including the ones that belong to O365Groups/Teams). Some of these are dependent upon source lists and therefore, the Content Type Hub is not an option because the list would have to be replicated into each of the /Sites Subsites. How are other amazing SharePoint gurus getting round this architecture? I've always created my SC's and CT's at the root of the domain, but when I created them at the http://tenant.sharepoint.com site, they were not visibile in the /Sites node. Thanks in advance!
Best practice for provisioning content types in modern team sites
We have a requirement to provision sites using a form we are building in SPFX web part to restrict who can create specific sites. This process requires lot of inputs from user to provision site and set default values in the site before users start using it. At the moment we have below requirements: Use of Document Set. Inherit content types from Content type hub Provision lists and libraries Associate the content type to the lists and libraries Add default content to lists and libraries Problem: We are using site design scripts for provisioning lists and libraries. Using site design scripts, Creation of content types from hub is not available, enabling of site collection features not available, adding of content to lists and library is not available. Solution tried: 1. Azure Automation - Written PowerShell script and wait for time till content types are synced to newly created sites (~30 mins). After site content types are available we are adding them to lists and libraries. And then adding default content to lists and libraries. But, problem is time taking and not sure if content types are synced 30 mins, sometimes we see over an hour. Script is growing over time for additional customization etc. 2. Pnp Provisioning - Use PnP provisioning template to download the schema from a existing site and then use that template to create site. This one has its own issues. At the moment for production use I like to know what is the best practice people are following to provision a modern site which uses content type hub content types?? If we use same content type id, name and fields in it in PnP provisioning template, are there any problems when the site syncs from content type hub in next run? thanks -Praveen.Access company branded templates from within Office apps
Does someone have more information about this feature? Link to the article: https://www.microsoft.com/en-us/microsoft-365/blog/2020/01/31/empower-firstline-workers-supercharge-search-whats-new-to-microsoft-365/ I am really interested but I couldn't find details about it anywhere. I guess (and hope) that with "company branded templates" they mean content types stored in the content type hub, and maybe this is related to the "modern content type gallery" recently announced in the message center (Roadmap ID https://www.microsoft.com/en-us/microsoft-365/roadmap?rtc=1&filters=&searchterms=57315). References supporting my guess: https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/announcing-new-file-template-management-for-document-library/ba-p/238374 https://techcommunity.microsoft.com/t5/sharepoint/is-it-possible-to-change-default-office-document-templates-for/m-p/113485 https://redmondmag.com/articles/2019/11/15/microsoft-sharepoint-changes-future-capabilities.aspxContent Type issue: Hidden columns not available when CT applied to List
I have a Content Type defined in our tenant's Content Type Hub. This CT is based on the "Event" CT which some fields added to support it's use for a Leave Request app I'm building. There are some columns that I want to only be available/editable via PowerApps and Flow, so I made them "Hidden" in the CT. I created it yesterday afternoon, so I know it's fully syndicated by now. In one of our Site Collections, I can view the Site Content Types and it shows up there with all of the columns that are shown in the Content Type Hub. Great! Next, I create a new ("modern") List and add that content type to it. This is where the weirdness starts. In the List Settings, I don't see any of the Hidden columns. From the Settings, if I click the CT name, no hidden columns. If I then click the Parent CT (so, the copy that exists at the site collection level), there are the hidden columns. See this video for a more detailed description. Thinking this was some kind of syndication issue, I went to the Content Type Hub and created a List there and added the CT to it - the same thing happens! Further thinking this may be a "modern vs classic" issue, I created a Custom List "App" and applied the CT to it - same thing. This is very frustrating. As our goal is to create a "standard" Leave Request/Approval process that can be rolled out to various departments and groups having a standard and consistent Content Type is a must. I suppose another approach is to create a site script that creates the list when/where we need it, but if we need to change something in that list, without the syndication function, we'd need to make that change in each site/list individually.Push content types from Content Type Gallery to a hub
Previously I have been using the old Content Type Syndication Hub to distribute custom content types to all my sites. However, I was frustrated by how long it took to publish changes and have been looking to move to SharePoint new modern Content Type Gallery feature (https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/modernizing-sharepoint-managed-metadata-services-mms/ba-p/1277450 and https://www.intelogy.co.uk/blog/diving-into-sharepoint-onlines-revamped-term-store-and-content-type-gallery/. On Microsoft's site, they specifically say you can push content types from the Gallery to hub sites for distribution to associated sites, and they even show this feature in a video: https://docs.microsoft.com/en-us/microsoft-365/contentunderstanding/push-content-type-to-hub However, on my view, I have no option to push content types to a hub. (This is a brand new 'test' content type so there shouldn't be a problem with it being from a legacy content type hub, and I do have a proper modern hub site and associated sites). Is there some hidden setting I need to turn on to enable this feature? EDIT: Or perhaps this feature isn't necessary, since types in the Content Type Gallery automatically push to all sites in my tenant? (But if so, why does Microsoft document the feature...?)
SharePoint Online Content Type Template .xlsm
Hi Folks, Just wondering if anyone has tried to create a Content Type with a custom template of .xlsm? According to Microsoft an .xlsm file should open in EXCEL online with the Macros disabled. We have a requirement of a content type with a custom template with the file type of .xlsm and to open online so it autosaves back into the Doc Lib - when we click on new within the Doc Lib it automatically tries to open in the desktop app and says it cant find the file? Wondering if anyone has came across this before?Content Type Hub
Has anyone else experienced issues with the CT hub? I've uploaded multiple taxonomies for the various business units, and then created Managed Metadata columns to be attached to their content types. Problems: 1) When i try to attach the term set to the the column, SP can't see the terms so there's nothing to attach to - even though the term set exists/ is visible in the term store manager. 2) Where some libraries have their Term Set attached and the metadata has been applied to a document, it can't be changed.... When opening the modern document properties fly-out panel and selecting the MM field to change, the dialogue box shows 0 terms available. Its almost as though the Taxonomy has been deleted 3) Some of the documents that have had the MM applied, the term sometimes shows as a number. I'm guessing that it the number of where the term sits within the Taxonomy. For example, instead of showing correctly as "Policy" it might show as "27" Clearly the Content Type Hub has "crashed" but need to find a solution. Anything created and tagged beforehand is ok, as long as the metadata is changed. Tried creating new term set manually (no problem encountered) but always goes back to not being able to attach it to the new column. HEEEELLLLLLLP!Content Type Republish from Content Type Hub has removed custom columns added at team site level
Hi Based on the Microsoft resources available on how Content Type publishing and republishing interacts with team site level customisation, I'm seeing an unexpected effect. https://support.office.com/en-us/article/Create-and-edit-content-types-3D5D45AF-608D-4183-8D51-073095FE0312#__toc239159103 "If the list content type has been customized with additional attributes that the parent content type does not have, such as extra columns, these customizations will not be overwritten" The column was created at team site level and added to the document library, with the option "Add to all content types" selected. Following a republish operation on the two content types shown in red, the additional column was removed from both of them. What have I missed?
