Cli-microsoft365: m365 spo web set fails with "Error: _ is not a valid web property"

Created on 12 Nov 2020  路  4Comments  路  Source: pnp/cli-microsoft365

Description

Calling spo web set fails with the error Error: _ is not a valid web property for any command-line parameter passed to it.

_e.g. Simple case_

m365 spo web set --webUrl "https://tenant.sharepoint.com/sites/siteurl" --title "HR Portal"

Other variations I've tried and result in the same error;

m365 spo web set --webUrl "https://tenant.sharepoint.com/sites/siteurl" --title "HR Portal"
m365 spo web set -u "https://tenant.sharepoint.com/sites/siteurl" -t "HR Portal"
m365 spo web set -u https://tenant.sharepoint.com/sites/siteurl -t HRPortal

Attempting to set some of the other properties supported by the command, such as --headerEmphasis or --headerLayout, yields the same result

I get the same error whether I use PowerShell on Mac OS or bash, I haven't tried on Windows.

Steps to reproduce

As above

Expected result

To be able to set web properties as per documentation

Environment

  • OS: Mac OS Catalina 10.15.7
  • PowerShell: 7.1.0
  • Bash: 3.2.57(1)-release
  • CLI: 3.2.0
bug work in progress

Most helpful comment

Thank you for reporting @phillipharding and apologies for the trouble.

This has appeared a few times in other commands and looks like a result of removing the vorpal dependency in the latest release (v3.2), if you downgrade to v3.1 you shouldn't see this issue.

@pnp/cli-for-microsoft-365-maintainers looks like this issue is affecting a number of commands so we should look into a other commands and apply a fix across the board.

All 4 comments

Thank you for reporting @phillipharding and apologies for the trouble.

This has appeared a few times in other commands and looks like a result of removing the vorpal dependency in the latest release (v3.2), if you downgrade to v3.1 you shouldn't see this issue.

@pnp/cli-for-microsoft-365-maintainers looks like this issue is affecting a number of commands so we should look into a other commands and apply a fix across the board.

Cheers @garrytrinder shall I close this issue?

I think this is a valid issue @phillipharding, let's keep it open until we have a fix

We've just released a preview version with this issue fixed. Thanks again for reporting @phillipharding 馃憦

Was this page helpful?
0 / 5 - 0 ratings