search

pnp / PnP-PowerShell

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

New-PnPSite parameter Lcid suddenly no longer recognized #2671

Closed joostvdlinden closed 4 years ago

joostvdlinden commented 4 years ago

Reporting an Issue or Missing Feature

I am using PnP PowerShell to automatically rollout a SharePoint modern Team Site. Suddenly the script is errorring out upon creating the site, the logs shows: New-PnPSite : A parameter cannot be found that matches parameter name 'Lcid'.

Expected behavior

I expect the script to create a new site using the correct country code

Actual behavior

The script is not creating the site and erroring out.

Steps to reproduce behavior

$title = $item["Title"] $alias = $item["alias"] $createsite = new-pnpsite -Type TeamSite -Title $Title -Alias $alias -Lcid 1043 -Description "Project site for $title"

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

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

SharePointPnPPowerShellOnline 3.2.1810.0

How did you install the PnP-PowerShell Cmdlets?

ghost commented 4 years ago

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

KoenZomers commented 4 years ago

@joostvdlinden I see you're still using a very old PnP PowerShell version: 3.2.1810.0 or in other words October 2018. Around that time the LCID parameter has been added to PnP PowerShell. Can you first ensure you're using the latest PnP PowerShell version and try it again to see if you still run into the same problem?

joostvdlinden commented 4 years ago

@joostvdlinden I see you're still using a very old PnP PowerShell version: 3.2.1810.0 or in other words October 2018. Around that time the LCID parameter has been added to PnP PowerShell. Can you first ensure you're using the latest PnP PowerShell version and try it again to see if you still run into the same problem?

Hi @KoenZomers, I already forgot that I had opened this issue. Otherwise I would have updated this issue. I had indeed discovered that the version was outdated. After updating PnP PowerShell the issue was resolved. Thanks for helping out anyway.