Forum Discussion
PnP Provisioning Framework - Referenced content type not available in site or template
Are you using a Developer tenant in SP Online? I'm asking cos that content type ID has only a search result in the entire Google here!:
https://github.com/SharePoint/sp-dev-docs/blob/master/workbench.aspx
Not sure why PnP is adding all these lists when the language is none-english, but if I'm right with my assumptions, I sugest you to test the same from a none-developer SP Online tenant, as that content type seems very specific to the new SP Development framework, and is not available in your On Prem tenant.
Let us know how it works.
It is not a Developer Tenant. Not sure where this contenttype originates from, and as I wrote it only appears in non-english templates.
For now I have solved it by having code like the following, running on the loaded template when provisioning on-prem:
ContentTypeBinding bindingToLookFor = new ContentTypeBinding(); bindingToLookFor.ContentTypeId = "0x0101009D1CB255DA76424F860D91F20E6C4118"; var offendingLists = template.Lists.Where(l => l.ContentTypeBindings.Contains(bindingToLookFor)); foreach (var l in offendingLists) { l.ContentTypeBindings.Remove(bindingToLookFor); }
- Luis MañezSep 23, 2016MVPIt's really weird. I tested the provisioning framework some tima ago on a non-english tenant and worked fine. That content type is not documented anywhere, so I'd still think that is something related with that tenant. Anyway, thanks for sharing the workaround!
- Malathi SekkappanMar 17, 2017Copper Contributor
I am using US English, and I am getting the same error while using the team site, I am using the latest PnP ver 2.13.1703. Sometimes, it works though. Any ideas?
- Luis MañezMar 20, 2017MVPInteresting. Now there's much more information about that Content Type. This CT is the one used in Modern Sites, to specify Modern Pages:
https://msdn.microsoft.com/en-us/pnp_articles/modern-experience-customizations-customize-pages
The only thing that I can think, is that if you Export the template from a Modern Site, and apply it to a non-modern site, you could get that issue, as the CT could be not present in a non-modern site.
Can you elaborate the case when it works?
Thanks.