Christian Zuellig

if you use a PnP-XML-Template you just set it like this - and you good to go. By code you can use CSOM Context.Web.SupportedUILanguageIds to read it and Context.Web.AddSupportedUILanguage or...

Ok - was not aware that there is a difference but can change to use pnpcorecontext as in ObjectClientSidePages. i can do the change next weekend and let you know.

You might has to check for DisableCustomAppAuthentication. You can use https://pnp.github.io/powershell/cmdlets/Set-PnPTenant.html to set these setting. Please be aware that change is not immediate active - according to others after 15min...

@jansenbe - the issue with webparts on collapsible sections is happening on out-of-the-box site collections - is unrelated to pnp (sorry for confusion)

I can provide some sample Error from our Logs - here it's when creating folder, but it happens at different functions within PnP Apply - for example while CreateView for...

i changed #301 in order to retry on SocketError. My Test with loop like above but counting up a list entry in order to see if in any chance the...

Looking at logs at our end i come to the conclusion that we need a shared Backoff-/Retry-state since there can be for example 6 ApplyTemplate toward the same tenant using...

It seems that the current modern UI does actually change the FieldType according to the setting of AllowMultipleValues.

@jansenbe Source of Issue unclear. Change in UI Modern and Classic changes today the FieldType according to the selection of AllowMultipleValues when updating Field-settings. However it's possible to create a...

@jansenbe Hope this is what you are looking for: Export: https://github.com/pnp/pnpframework/blob/dev/src/lib/PnP.Framework/Provisioning/ObjectHandlers/ObjectListInstanceDataRows.cs TokenizeValue called for Export seems to act on FieldType only - therefore we should not export the issue Provision:...