PnP Remote Provisioning Engine Failed - Repost Page Content Type

%3CLINGO-SUB%20id%3D%22lingo-sub-219587%22%20slang%3D%22en-US%22%3EPnP%20Remote%20Provisioning%20Engine%20Failed%20-%20Repost%20Page%20Content%20Type%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-219587%22%20slang%3D%22en-US%22%3E%3CP%3EOn%20May%2018%20our%20PnP%20remote%20provisioning%20engine%20script%20began%20failing%20in%20our%20SharePoint%20online%20production%20(as%20did%20several%20others)%20environment.%26nbsp%3B%20The%20root%20cause%20for%20failure%20was%20a%20change%20to%20the%20Repost%20Page%20content%20type%20in%20SharePoint%20online.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fpgbhoyar.com%2F2018%2F06%2F06%2Fpnp-provisioning-error-field-not-found-issue-with-the-repost-page-content-type%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fpgbhoyar.com%2F2018%2F06%2F06%2Fpnp-provisioning-error-field-not-found-issue-with-the-repost-page-content-type%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FSharePoint%2FPnP-Sites-Core%2Fissues%2F1788%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FSharePoint%2FPnP-Sites-Core%2Fissues%2F1788%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOther%20than%20the%20two%20references%20above%2C%20I%20haven't%20seen%20anything%20about%20this%20in%20any%20of%20the%20PnP%20Remote%20Provisioning%20web%20pages%20and%20documentation%20or%20PnP%20quarterly%20updates%20(maybe%20I'm%20looking%20in%20the%20wrong%20places).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20failure%20in%20our%20PnP%20Remote%20Provisioning%20Engine%20script%20caused%20major%20disruption%20for%20our%20client%20and%20was%20totally%20unexpected.%20I'm%20trying%20to%20understand%20(I'm%20not%20a%20developer%3B%20I%20am%20the%20BA%20on%20the%20project)%20how%20we%20can%20avoid%20having%20something%20like%20this%20happen%20again.%26nbsp%3BCan%20we%20modify%20our%20existing%20script%20in%20some%20way%3F%20Hoping%20someone%20close%20to%20this%20project%20can%20help%20with%20some%20solid%20guidance.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBill%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

On May 18 our PnP remote provisioning engine script began failing in our SharePoint online production (as did several others) environment.  The root cause for failure was a change to the Repost Page content type in SharePoint online.  

 

https://pgbhoyar.com/2018/06/06/pnp-provisioning-error-field-not-found-issue-with-the-repost-page-co...

 

https://github.com/SharePoint/PnP-Sites-Core/issues/1788

 

Other than the two references above, I haven't seen anything about this in any of the PnP Remote Provisioning web pages and documentation or PnP quarterly updates (maybe I'm looking in the wrong places).

 

This failure in our PnP Remote Provisioning Engine script caused major disruption for our client and was totally unexpected. I'm trying to understand (I'm not a developer; I am the BA on the project) how we can avoid having something like this happen again. Can we modify our existing script in some way? Hoping someone close to this project can help with some solid guidance.  

 

Thanks! 

 

Bill 

 

 

 

 

0 Replies