cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
karamem0
Level: Powered On

'-EnvironmentName' parameter is better to rename to '-EnvironmentId'

In PowerApps PowerShell script functions, '-EnvironmentName' parameter requires GUID, but not name (e.g. "My Environment"). It is not suitable and many users may be confused, so rename to '-EnvironmentId'. 

2 REPLIES 2
Highlighted
PowerApps Staff jo
PowerApps Staff

Re: '-EnvironmentName' parameter is better to rename to '-EnvironmentId'

That's true, the semantics that we use throughout the cmdlets is that the identifier for a resource = {Resource}Name (e.g. EnvironmentName, AppName, etc.).

 

It's good feedback, however I hope it is clear from the examples we provide for each function.

karamem0
Level: Powered On

Re: '-EnvironmentName' parameter is better to rename to '-EnvironmentId'

For example, 'Id' parameter and 'Name' parameter are clearly distinguished in Azure PowerShell.

 

Get-AzureRmSubscription -SubscriptionId "yyyy-yyyy-yyyy-yyyy"
Get-AzureRmSubscription -SubscriptionName "Contoso Subscription 1"

 Therefore, users expect to accept GUID in 'Id' parameter.

Helpful resources

Announcements
thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Power Platform World Tour

Find out where you can attend!

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

fifthimage

Microsoft Learn

Learn how to build the business apps that you need.

Top Kudoed Authors (Last 30 Days)
Users online (5,444)