Forum Discussion
New-PnPTenantSite : LocaleId 2057 is not a supported locale.
The LCID you specify when creating your site collection determines the default language of the site and that works fine if you know the supported LCID's
I can imagine it would be convenient for you to be able to directly specify the regional settings as well. If it's really important to you, you could go and create your own PowerShell cmdlet based on the exsting one and provide for the additonal functionality that way. The available cmdlets are all Open Source on GitHub and scenario's like yours are great opportunities to contribute!
Thanks Paul.
Could you please let me know how do i go about changing a param.
This is a bit grey area for me, is it something that i have to make change to a shell.
First of all you'd need developer skills to get started or find someone who has. Windows PowerShell provides an SDK and allows developers to implement new cmdlets.
Easiest then is to find the implementation of the existing cmdlet in the Git Repository, see how it works and implement your requirements there
https://github.com/SharePoint/PnP-PowerShell/blob/08eb375ccf51ed8c04e8df13ae4fc617fda47377/Commands/Admin/NewTenantSite.cs
I won't go changing the existing param. Instead I'd add an (optional) additonal one (RegionLcid for example) or consider implementing a new cmdlet. Then implement the logic required to change the regional settings after the site has been created (as described in the blog I referred to in my first reply, for example).
General Guidance on how to contribute to PnP initiative is located here
https://github.com/SharePoint/PnP-PowerShell/blob/08eb375ccf51ed8c04e8df13ae4fc617fda47377/CONTRIBUTING.md
Hope this helps
Thanks Paul