Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invoke-PnPSiteTemplate and Convert-PnPSiteTemplate failing on template #475

Open
ohaak2 opened this issue Sep 30, 2021 · 0 comments
Open

Comments

@ohaak2
Copy link
Contributor

ohaak2 commented Sep 30, 2021

Invoke-PnPSiteTemplate and Convert-PnPSiteTemplate are failing on template.

I've first noticed this with Invoke-PnPSiteTemplate on several template that previously worked without any issues. Now the comand will acutally process the template, but is effectivly doing nothing.

I've recently tried to convert that template (still using an old schema 201805 or 201807) with Convert-PnPSiteTemplate. This here is all I get back from a full-featured template - the actual template part is stripped blank:

<pnp:Provisioning xmlns:pnp="http://schemas.dev.office.com/PnP/2021/03/ProvisioningSchema">
  <pnp:Preferences Generator="PnP.Framework, Version=1.6.0.0, Culture=neutral, PublicKeyToken=null" />
  <pnp:Templates ID="CONTAINER-">
    <pnp:ProvisioningTemplate Version="0" Scope="Undefined" />
  </pnp:Templates>
</pnp:Provisioning>

I had to migrate the templates manually to a later schema to get them working again. I manged to get them to 202002 and was then able to convert them to LATEST as well as directly apply them using Invoke-PnPSiteTemplate.

It really seems a breaking thing with some schema versions for both commands. Not exactly sure at which version it's breaking and on which version it's fine again. All I can say is, that I have the issue with 201805 and 201807 and it's working again with 202002.

Only thing I've noticed converting one of the templates from 202002 to LATEST then was, that in a template actually containing more then one ProvisioninTemplate childs only one gets converted - the other one (in my case only 2) was dropped. Converting them one by one and merging the outcome was - of course - possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant