Forum Discussion
Automated Deployment from Staging to Production (SharePoint Online)
- Generally site pages could be skipped as site pages is already created when creating the site. I had a similar issue with an older version of PnP template with Site Assets, removed that section and it worked fine. Also I will recommend not to remove the webhooks as they add parallel processing. For an overview steps and more options, check here - https://asishpadhy.com/2018/11/09/walkthrough-of-pnp-provisioning-process-using-powershell/
Yes, I familiar with PnP PowerShell to do export/import Content Type, Site Columns.
Surprisingly that PnP is able to do export site template. It's pretty a big help for me.
FYI. Get-SPOProvisioningTemplate is changed to Get-PnPProvisioningTemplate.
Another question is that PnP Provisioning able to export site collection includes all subsites, sub-subsites, doc libraries and list, content type, site columns, managed metadata, all configurations and look and feel as well?
Any limits for this PnP Provisioning regarding to size, the complexity or any customization?
Thanks.
Thanks for your info.
Currently it doesn't have subsite and able to export.
However I hit the error during the import site provisioning to testing site (New site for document center template).
Error: [SchemaFormatter] [0] [Error] Template is not valid: The required attribute 'ServerNotificationUrl' is missing.
Please advice.
I manage to resolve the error with removing all webhook elements..
However do you face this problem before? Out of range..
PowerShell_ISE.exe Information: 0 : 2018-08-14 22:30:16.9085 [List instances] [3] [Debug] Creating list Site Pages failed: Specified argument was out of the range of valid values.
Parameter name: value : at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()
at Microsoft.SharePoint.Client.ClientRequest.<ExecuteQueryToServerAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SharePoint.Client.ClientRequest.<ExecuteQueryAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SharePoint.Client.ClientRuntimeContext.<ExecuteQueryAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SharePoint.Client.ClientContext.<ExecuteQueryAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SharePoint.Client.ClientContextExtensions.<ExecuteQueryImplementation>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SharePoint.Client.ClientContextExtensions.ExecuteQueryRetry(ClientRuntimeContext clientContext, Int32 retryCount, Int32 delay, String userAgent)
at Microsoft.SharePoint.Client.FieldAndContentTypeExtensions.SetDefaultContentType(List list, ContentTypeId contentTypeId)
at OfficeDevPnP.Core.Framework.Provisioning.ObjectHandlers.ObjectListInstance.ConfigureContentTypes(Web web, List list, ListInstance templateList, Boolean isNewList, PnPMonitoredS
cope scope)
at OfficeDevPnP.Core.Framework.Provisioning.ObjectHandlers.ObjectListInstance.CreateList(Web web, ListInstance templateList, TokenParser parser, PnPMonitoredScope scope, Boolean i
sNoScriptSite)
at OfficeDevPnP.Core.Framework.Provisioning.ObjectHandlers.ObjectListInstance.ProvisionObjects(Web web, ProvisioningTemplate template, TokenParser parser, ProvisioningTemplateAppl
yingInformation applyingInformation) 47668ms 9b146cc1-12bc-4e72-96a2-4f5a434cdcfc
PowerShell_ISE.exe Information: 0 : 2018-08-14 22:30:16.9223 [List instances] [3] [Debug] Code execution scope ended 47681ms 9b146cc1-12bc-4e72-96a2-4f5a434cdcfc
PowerShell_ISE.exe Information: 0 : 2018-08-14 22:30:16.9254 [Provisioning] [3] [Debug] Code execution scope ended 106825ms 9b146cc1-12bc-4e72-96a2-4f5a434cdcfc
Apply-PnPProvisioningTemplate : Specified argument was out of the range of valid values.- Generally site pages could be skipped as site pages is already created when creating the site. I had a similar issue with an older version of PnP template with Site Assets, removed that section and it worked fine. Also I will recommend not to remove the webhooks as they add parallel processing. For an overview steps and more options, check here - https://asishpadhy.com/2018/11/09/walkthrough-of-pnp-provisioning-process-using-powershell/