search

pnp / PnP-PowerShell

SharePoint PnP PowerShell CmdLets
https://pnp.github.io/powershell
Other
990 stars 663 forks source link

Enable-PnPFeature Document Sets site collection feature not working consistently #2733

Open joostvdlinden opened 4 years ago

joostvdlinden commented 4 years ago

Notice: many issues / bugs reported are actually related to the PnP Core Library which is used behind the scenes. Consider carefully where to report an issue:

  1. Are you using Apply-PnPProvisioningTemplate or Get-PnPProvisioningTemplate? The issue is most likely related to the Provisioning Engine. The Provisioning engine is not located in the PowerShell repo. Please report the issue here: https://github.com/pnp/PnP-Sites-Core/issues.
  2. Is the issue related to the cmdlet itself, its parameters, the syntax, or do you suspect it is the code of the cmdlet that is causing the issue? Then please continue reporting the issue in this repo.
  3. If you think that the functionality might be related to the underlying libraries that the cmdlet is calling (We realize that might be difficult to determine), please first double check the code of the cmdlet, which can be found here: https://github.com/pnp/PnP-PowerShell/tree/master/Commands. If related to the cmdlet, continue reporting the issue here, otherwise report the issue at https://github.com/pnp/PnP-Sites-Core/issues

Reporting an Issue or Missing Feature

In my PnP PowerShell script I am rolling out a Team Site. To use managed metadata features I am activating the following SharePoint features:

$EnableDocSetFeature = Enable-PnPFeature -Identity 3bae86a2-776d-499d-9db8-fa4cdc7884f8 -Scope Site -ErrorAction Stop

$EnablePushNotificationsFeature = Enable-PnPFeature -Identity 41e1d4bf-b1a2-47f7-ab80-d5d6cbba3092 -Scope Web -ErrorAction Stop

$EnableTaxonomyFeature = Enable-PnPFeature -Identity 73ef14b1-13a9-416b-a9b5-ececa2b0604c -Scope Site -ErrorAction Stop

I notice that periodically this feature is not run properly. I observe that there is no exception or error showing up in the Azure Runbook result, but that the site feature is not disabled. When I re-run the job, it runs successfully without changing anything.

Expected behavior

Consistent behavior.

Actual behavior

No error message, but the site feature not being activated. I observe this through Site Settings -> Site Collection features. If I re-run the job, it runs fine.

Steps to reproduce behavior

Please review code above

Which version of the PnP-PowerShell Cmdlets are you using?

What is the version of the Cmdlet module you are running?

SharePointPnPPowerShellOnline module version 3.22.2006.2

How did you install the PnP-PowerShell Cmdlets?

Azure PowerShell Gallery -> Import module

ghost commented 4 years ago

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

Shaan0321 commented 3 years ago

Is there is any update ? I am facing same issue and i am not able to assign custom permissions using PNP

joostvdlinden commented 3 years ago

Is there is any update ? I am facing same issue and i am not able to assign custom permissions using PNP

Unfortunately not...