[BUG] Enable-PnPFeature ignore -Force parameter

[stevebeauge]

Reporting an Issue or Missing Feature

Reporting an issue

Expected behavior

Calling Enable-PnPFeature with the -Force parameter should not fail

Actual behavior

If the feature is already activated, the command fails:

Enable-PnPFeature: c:\some\path\script.ps1:168:3
Line |
 168 |    Enable-PnPFeature -Identity $FeatureTaxonomy -Scope Site -Force -Co …
     |    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Feature was already activated (Parameter 'id')

Steps to reproduce behavior

$siteConn = Connect-PnPOnline -Url $SiteUrl -ReturnConnection -ClientId:XXXX -Interactive -PersistLogin
$FeatureTaxonomy = "73ef14b1-13a9-416b-a9b5-ececa2b0604c" 
Enable-PnPFeature -Identity $FeatureTaxonomy -Scope Site -Force -Connection $siteConn

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

3.1.0

Which operating system/environment are you running PnP PowerShell on?

• Windows
• Linux
• MacOS
• Azure Cloud Shell
• Azure Functions
• Other : please specify

[reshmee011]

Before running the cmdlet, you can check whether the feature is already activate like:

$FeatureTaxonomy = "73ef14b1-13a9-416b-a9b5-ececa2b0604c" 
 $feature= Get-PnPFeature -Identity $FeatureTaxonomy -Scope Site

 if(!$feature.DefinitionId)
            {
                # Enable taxonomy feature
                Enable-PnPFeature -Identity $FeatureTaxonomy -Scope Site -Force
            }

The intent behind force parameter is to skip user confirmation to automate the execution, it can't be used to hide any error messages.

Try the suggested script and share the outcome.

[stevebeauge]

This is not what the documentation states:

-Force

Specifies whether to overwrite an existing feature with the same feature identifier. This parameter is ignored if there are no errors.

The workaround you suggested may work but it should works as mentioned in the doc

[reshmee011]

The documentation will need to be updated to remove the force parameter as it is not being used to suppress or bypass errors. @NishkalankBezawada : your views on how to handle it?