Bert Jansen

Good feature request @joerodgers. Given this means updating PnP PowerShell I'll move this issue to the PnP PS repo.

@Leviani : moved.

+1, seeing same type of random errors

This seems to be backend related: the errors randomly popup and we've not made changes in the places where the errors are thrown. I'll need to some more testing and...

I do see these errors when I'm deleting a site collection and creating a new site collection with the same name immediately afterwards... @awdhaan : does my scenario also apply...

Hi @bricenocar , this change conflicts with the change done a while ago by @czullu (https://github.com/pnp/PnP-Sites-Core/pull/2610). Can you cross check this PR with him and if needed update. @czullu's case...

given UpdateChildren in FieldRef defaults to true your code change now will trigger update of child content types whereas we today do not do that. This will possibly impact existing...

When we read a template the fieldref property UpdateChildren is always set to true, whereas we currently block updating child content types. So your PR does introduce a change in...

Nice catch @gautamdsheth . Given this impacts the existing templates (eg all our templates in the provisioning service) we need to coordinate patching the provisioning service and the templates aligned...

Thanks @czullu , I've assigned @erwinvanhunen to this PR