microsoft / powerplatform-vscode

The Power Platform VSCode extension makes it easy to manage Power Platform environments and allows the developer to create, build and deploy Power Platform solutions, packages and portals.

Power Platform Extension

The Power Platform extension makes it easy to manage Power Platform environments and allows the developer to create, build and deploy Power Platform solutions, packages and portals.

Installing this extension will also make the latest Power Platform CLI (aka pac) available in your VSCode terminal.

"Power Platform CLI Exposed" Series

Daniel Laskewitz talks with members of our team about PAC CLI, Solutions, Power Pages, Data & Tool, Pipelines, and PCF

Power Platform CLI Exposed

Requirements

• VSCode >= 1.73.0
• Windows: .NET 4.8
• macOS/Linux/WSL: .NET 6.0+ SDK

Getting Started

Open the VS Code Terminal (Terminal | New Terminal) and type in:

> pac
Microsoft PowerPlatform CLI

Usage: pac [admin] [application] [auth] [canvas] [help] [org] [package] [paportal] [pcf] [plugin] [solution] [telemetry]

  admin                       Work with your PowerPlatform Admin Account
  application                 Commands for listing and installing available DataVerse applications from AppSource
  auth                        Manage how you authenticate to various services
  canvas                      Operating with Power Apps .msapp files
  help                        Show help for the Microsoft PowerPlatform CLI
  org                         Work with your Dataverse Organization
  package                     Commands for working with Dataverse package projects
  paportal                    Commands for working with PowerApps portal website
  pcf                         Commands for working with PowerApps component framework projects
  plugin                      Commands for working with Dataverse plugin class library
  solution                    Commands for working with Dataverse solution projects
  telemetry                   Manage telemetry settings

The pac CLI will show you the available command nouns with a short description. To get detailed help for each noun, use the built-int help screens for each command, e.g.:

> pac solution help
Microsoft PowerApps CLI

Usage: pac solution [init] [add-reference] [list] [delete] [online-version] [version] [import] [export] [clone] [publish] [upgrade] [add-license] [check] [create-settings] [pack] [unpack]

  init                        Initializes a directory with a new Dataverse solution project
  add-reference               Adds a reference from the project in the current directory to the project at 'path'
  list                        List all Solutions from the current Dataverse Organization
  delete                      Delete Dataverse Solution from the current Dataverse Environment
  online-version              Sets version for solution loaded in Dataverse environment.
  version                     Update build or revision version for solution
  import                      Import the Dataverse Solution into the current Dataverse Environment
  export                      Export a Dataverse Solution from the current Dataverse Environment
  clone                       Create a solution project based on an existing solution in your Organization
  publish                     Publishes all customizations
  upgrade                     Option to stage the Dataverse solution for upgrade
  add-license                 Add license and plan info to solution
  check                       Upload a Dataverse Solution project to run against the PowerApps Checker Service
  create-settings             Create a settings file from solution zip or solution folder.
  pack                        Package solution components on local filesystem into solution.zip (SolutionPackager)
  unpack                      Extract solution components from solution.zip onto local filesystem (SolutionPackager)

To then view all solutions installed in the selected environment:

> pac solution list
Connected to...vscode-test
Listing all Solutions from the current Dataverse Organization...

 Index      Unique Name                                        Friendly Name                                                Version


 [1]        Cr4323c                                            Common Data Services Default Solution                        1.0.0.0

Feedback & Questions

Please use the issues tracker in the home repo: https://github.com/microsoft/powerplatform-vscode/issues

Contributing

This project will welcome contributions in the near future. At this stage, we're not ready for contributions, but do welcome your suggestions via this repository's issue tracker.

See details in CONTRIBUTING

Code of Conduct

See details in CODE_OF_CONDUCT

Security issues

Please report any security concerns or issues as described in this SECURITY document.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

powerplatform-vscode's Issues

Backup Label and Notes doesn't do anything

While taking backup of the environment, even though when you past label value it doesn't get reflected in the actual backup instead it displays the time when the backup was taken.

To repo:

• authenticate through pac auth with user credential who has SA rights to the environment
• pac admin backup -env 'environment-url-where-you-want-to-take-backup' -l 'backup-from-pac-cli'

Once complete,

• go to Power Platform Admin center
• open the envrironment which you choose to take backup of,
• select Backups > Restore or manage
• Select 'Manual'

Expected: you should see backup with label 'backup-from-pac-cli'
Actual: you will see backup with label 'date + time when the backup was taken'

Improve commands exit code for scripting

Description

pac auth select -n ... always return True

I'm creating scripts to help manipulate my solutions in a multi developer setup.
But when I select my authentication, it always returns true.

PS > pac auth select -n NonExistingAuth
Microsoft PowerPlatform CLI
Version : 1.14.2+g7205df7

Erreur : Il n'existe aucun profil d'authentification portant le nom « NonExistingAuth »

Utilisation : pac auth select [--index] [--name]

  --index                     Index du profil à activer (alias : -i)
  --name                      Nom du profil à activer (alias : -n)
PS > $?
True

So I need to catch this error somehow, to make sure were not importing a solution if we're not targeting the expected environement.

Suggestion

Return a non zero value if there is no authentication profile that matches the requested name

P.S. : And thanks a ton for your amazing work with pac ;)

Execution status is not set by pac

When a pac command fails it should be possible to detect via the last execution variable, e.g $? (https://docs.microsoft.com/en-gb/powershell/module/microsoft.powershell.core/about/about_automatic_variables?view=powershell-7.2#section-1) in PowerShell, similar in bash.

This is currently not working. See example below:

Find out whether a Solution is Managed or Unmanaged

I'm looking to export all unmanaged Solutions from a given environment in an automated way.
When doing pac solution list this gives me a list of all solutions.
However, there seems to be no way currently to find out which Solutions are managed or unmanaged.
This is an issue because managed Solutions can not be exported.

Would it be possible to add a flag to the pac solution list command? E.g. for --unmanaged to only return the list of unmanaged solutions?

Live preview icon shows as empty

When using VScode the preview icon just shows an empty square. I thought I hadn't got the setup correct and was wondering why it wasn't there.

It still works when you click on it.

Power Platform CLI (PAC) for PowerShell?

Do you know if there are plans to release a PowerShell version of PAC (e.g. a set of cmdlets that expose the same functionality as the existing PAC)?

Thanks,
Ben

pac paportal download --overwrite throw exception

When using the --overwrite option to download powerportal code, it throws exception as below.
I tried to run VS Code in admin mode, still same issue

List of solutions is not possible on Dataverse for Teams

The command pac solution list fails on Dataverse for Teams.

Command:

pac solution list --environment-id <my-teams-environment-id>

Result:

Connected to...Team My Teams-Team
Listing all Solutions from the current Dataverse Organization...
Microsoft PowerPlatform CLI
Version: 1.10.4+gf23be2f

Error: The 'RetrieveOrganizationInfo' is only allowed to be accessed from OData endpoint in Dataverse for Teams offering. EnitytName: none

Unpack fails with error

ERROR RETURNED: Error: An item with the same key has already been added.

PS C:\Users\Dave> cd "F:\OneDrive - Stabilify, LLC\PowerApp Projects\Packages\CaseworkerHub-v713-COPY_20220415195828\Microsoft.PowerApps\apps\10012562781360855322"
PS F:\OneDrive - Stabilify, LLC\PowerApp Projects\Packages\CaseworkerHub-v713-COPY_20220415195828\Microsoft.PowerApps\apps\10012562781360855322> pac canvas unpack --msapp N2d96f620-b358-4fdf-aaa5-7d4c43f720d9-document.msapp --sources "F:\OneDrive - Stabilify, LLC\PowerApp Projects\Packages\CaseworkerHub-v713-COPY_20220415195828\Microsoft.PowerApps\apps\10012562781360855322\Extract"
Warning: canvas unpack is in preview, and functionality is not guaranteed. Use extreme caution if using in a production environment. For more information see aka.ms/paccanvas
UnPack from F:\OneDrive - Stabilify, LLC\PowerApp Projects\Packages\CaseworkerHub-v713-COPY_20220415195828\Microsoft.PowerApps\apps\10012562781360855322\N2d96f620-b358-4fdf-aaa5-7d4c43f720d9-document.msapp-->F:\OneDrive - Stabilify, LLC\PowerApp Projects\Packages\CaseworkerHub-v713-COPY_20220415195828\Microsoft.PowerApps\apps\10012562781360855322\Extract
Microsoft PowerPlatform CLI
Version: 1.14.2+g7205df7

Error: An item with the same key has already been added.

Error PA3003: Parse error: Property should be at same indent level

Formatting in vs code drops the indentation in line 350 of the .yaml file.
When packing the source files it throws a PA3003: Parse error

using the command >pac canvas pack ...

348        Text: |-
349            ="Click the blue Save disk in the top left to submit a Rapid Response or to save any changes.
350
351            Incident Classification:
352            Light - <4 hrs
353            Serious - >4 & <24hrs"

pac 1.9.8 fail to unpack my canvas app with 'non recoverable error'

Since yesterday, pac is not longer able to unpack my canvas app.

The current (latest) pac version is 1.9.8

The command:

pac canvas unpack --msapp ./app.msapp --sources ./src

Error Output

UnPack from R:\test\app.msapp-->R:\test\src
Sorry, the app encountered a non recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id:95125a45-24c1-4dca-90db-b65e216c943e

An older version (1.9.4 from yesterday) works:

pac install 1.9.4
pac use 1.9.4
pac canvas unpack --msapp ./app.msapp --sources ./src

The output and result is as expected:

UnPack from R:\test\app.msapp-->R:\test\src                                                                                                                                                                      source format version: 0.24

--allowDelete has wrong instruction in the help section

Based on the help command in pac module, if you want to unpack solution, this is the instruction you get i.e.
--allowDelete Dictates if delete operations may occur [Yes|No]; default: No. (alias: -ad)

However, if you try to run the unpack command with the value of 'Yes' or 'No' in --allowDelete flag, it errors out with this error message:

if you run the same command with true/false boolean value, i.e. --allowDelete true or --allowDelete false, the command runs successfully. The solution unpack help instruction needs to be updated.

To replicate the issue:

1. Run this command:
   pac solution unpack help

2. Check the help instruction for '--allowDelete' flag. It should display this:
   

3. Export managed solution from Power platform makers portal

4. Run this command to unpack the solution based on the instruction displayed from step 1.
   pac solution unpack --zipfile [--folder] --packagetype 'managed' --allowDelete 'No'

5. You should get this error message:
   

--convert-to-managed option may not be working

We are utilizing Powerplatform CLI v1.9.4+gbda9f20 in our project to build a CI and release pipeline for deployment of solutions. I noticed that I am not able to make the --convert-to-managed option to work. My goal was to import an unmanaged solution into an upstream environment and convert it to a managed solution. Here are examples of the command that I am using -
pac solution import -ap -a -cm -p "C:\Users\adhishgupta\Downloads\my_unmanaged.zip"

OR
pac solution import -p "C:\Users\adhishgupta\Downloads\my_unmanaged.zip" --async --convert-to-managed

Each time, the solution is imported as unmanaged successfully but not converted to managed. Am I missing something or is there a bug?

Inconsistent alias to set instance using templates while creating and resetting instance

while creating instance the alias to configure template is '-tm' but while resetting instance the alias is '-t'. Also, the reset help command shows the examples starting with -tm which isn't right. since both are setting template, i believe both create and reset command should have same alias to set template during the creation or reset of instance.

e.g.
To Create instance:
pac admin create -n 'sanjeev-poc' -r 'usgov' -t 'sandbox' -tm 'D365_CustomerService'

To Reset instance:
pac admin reset -env [guid] -t 'D365_CustomerService'

Create Help Image:

Reset Help Image:

Non-recoverable error, terminated

CMD:
pac canvas unpack --msapp <PATH>

Result:
Sorry, the app encountered a non recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id: 1d90342e-e1d1-445f-96a2-6103cfd90015, Exception Type: System.ArgumentException

Comments:
The application looks to be unpacked in the explorer. Assets, Entropy, pkgs, Src all created. However due to "non recoverable error", unpack msapp files step in Azure DevOps Pipelines errors out entire pipeline.

Error using in codespace or wsl

I use the pac command in VS Code(with extension installed) in a CodeSpace, the command failed.

1. Use on the url, failed with below
   Error: Unable to open a web page using xdg-open, gnome-open, or kfmclient tools. See inner exception for details. Possible causes for this error are: tools are not installed or they cannot open a URL. Make sure you can open a web page by invoking from a terminal: xdg-open https://www.bing.com
   Failed to locate a utility to launch the default web browser.

2. Use url + correct username/password, always got auth failed, do we need to install additional package on linux?
   Error: AADSTS50126: Error validating credentials due to invalid username or password.
   Trace ID: f927415e-9ca9-4d21-8cb8-835ed52bda00
   Correlation ID: 0a88d6ef-34bc-415b-a7d0-b46258423b0c
   Timestamp: 2021-11-02 09:58:35Z

macOS: 'pac auth create' interactive authN flow not yet working

current workaround: supply credentials via command line parameters:

• 'pac auth create --kind <CDS|ADMIN> --username --password
  or:
• 'pac auth create --kind <CDS|ADMIN> --applicationId --tenant --clientSecret

Add command to set security group of instance during create or reset of instance

We have a need where we need to reset the instance and install the master solution every once in a while. With current pac command, most of the stuff can be automated except for setting security group of the instance. Since the security group cannot be set while running reset command, the service account that is being used to automate the process loses access after the reset is complete because of missing security group. It would be nice to set the security group during the process of reset of instance so that when the instance comes back after reset, the service account won't lose access and can perform other tasks against the environment. Same request during the creation of the new instance.

example:

`
pac admin reset -env [URL or ID] -security-group-id [AD-Group-Guid-ID]

Downloading code from a PowerApps website and overwriting causes CLI to crash

I'm experimenting with this tool to use with my team and wanted to start developing without using the in-built power platform editor, so when I download changes from the power apps website I want to overwrite the files by adding the flag: --overwrite but the CLI crashes. See screenshot below

Sorry, the app encountered a non recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id: 201e83d1-ee78-46b7-b8f4-2d97cf68c432, Exception Type: System.FormatExceptionThe diagnostic logs can be found at: c:\Users\gemartinez\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\logs\pac-log.txt

Error creating Admin profile for UsGov cloud instance

i am trying to add admin profile for our UsGov instance and it keeps erroring out with this error message.

Here is the command i ran:
auth create -k ADMIN -ci UsGov

PowerApps Cli creating a usersettings.json in the wrong path

Describe the bug

The PowerApp Cli seems to be creating the usersetting.json in a wrong path. Instead of creating in user's Library folder, it seems to be creating in the application folder. This is happening in MacOS. The attached screenshot will help explain this better.

Version: 1.15.3+g79950a8

To Reproduce

• Install Power Platform Tools for Visual Studio Code (Mac M1)
• Execute any Cli commands
• A new folder structure gets created inside the application folder instead of ~/Library

Screenshots

`pac package deploy` times out when upgrade detected

When an existing solution need to be upgraded pac package deploy is timing out, e.g.

pac package deploy -p .\PackageDeploy.dll --logFile installog2.txt --logConsole

Gives the following logs.

Are there any timeout or config settings that can be used to tune? This tip from @scottdurow doesn't seem to work.

Thanks!

PackageDeployVerb Information: 8 : Message: ************** Solution IMPORT *****************
PackageDeployVerb Information: 8 : Message: Starting Processing Of Solution: My Amazing Solution(MyAmazingSolution), Version: 1.0.0.1, PackageVersion: 9.2
Beginning load of solution My Amazing Solution, version: 1.0.0.1.
PackageDeployVerb Information: 8 : Message: MyAmazingSolution : User Code Execution : OP=OverrideSolutionImportDecision : Status=Execute
PackageDeployVerb Information: 8 : Message: MyAmazingSolution : User Code Execution : OP=OverrideSolutionImportDecision : Status=Complete : Duration=00:00:00.0002229
PackageDeployVerb Information: 8 : Message: MyAmazingSolution - Processing Solution - Inbound version: 1.0.0.1 - Deployed Version 1.0.0.0, System Determined Import Action: Import
PackageDeployVerb Information: 8 : Message: MyAmazingSolution - ImportSolution - Overwrite solution version My Amazing Solution with version 1.0.0.1
PackageDeployVerb Information: 8 : Message: MyAmazingSolution - Updating solution Version: 1.0.0.0 to Version : 1.0.0.1 - Importing Holding Solution - USING 7.2+ API
PackageDeployVerb Information: 8 : Message: MyAmazingSolution : User Code Execution : OP=PreSolutionImport : Status=Execute
PackageDeployVerb Information: 8 : Message: MyAmazingSolution : User Code Execution : OP=PreSolutionImport : Status=Complete : Duration=00:00:00.0002173
PackageDeployVerb Information: 8 : Message: ImportSolution - Async Supported = True
PackageDeployVerb Information: 8 : Message: DeleteAndPromote - Async Supported = True
PackageDeployVerb Information: 8 : Message: MyAmazingSolution - Executing Solution Import - UploadHoldingSolutionV2
PackageDeployVerb Information: 8 : Message: MyAmazingSolution - Fetching Data
PackageDeployVerb Information: 8 : Message: MyAmazingSolution - Import Progress is : 100
PackageDeployVerb Information: 8 : Message: MyAmazingSolution Solution Import Result = success - Duration: 00:01:16.9528092
PackageDeployVerb Information: 8 : Message: MyAmazingSolution - Updated solution Version: 1.0.0.0 to Version : 1.0.0.1
PackageDeployVerb Information: 8 : Message: MyAmazingSolution : User Code Execution : OP=RunSolutionUpgradeMigrationStep : Status=Execute
PackageDeployVerb Information: 8 : Message: MyAmazingSolution : User Code Execution : OP=RunSolutionUpgradeMigrationStep : Status=Complete : Duration=00:00:00.0003294
PackageDeployVerb Information: 8 : Message: MyAmazingSolution - Updating solution Version: 1.0.0.0 to Version : 1.0.0.1 - Deleting Holding Solution
PackageDeployVerb Information: 8 : Message: MyAmazingSolution - Executing Solution Import - PromoteHoldingSolutionV2
Microsoft.Xrm.Tooling.Connector.CrmServiceClient Error: 2 : ************ TimeoutException - DeleteAndPromote : Delete and Promote Solution to New version(DeleteAndPromoteSolutionRequest) |=> The request channel timed out while waiting for a reply after 00:01:59.9819968. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
Source  : mscorlib
Method  : HandleReturnMessage
Date    : 17/04/2022
Time    : 19:19:09
Error   : The request channel timed out while waiting for a reply after 00:01:59.9819968. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
Stack Trace     : Server stack trace:
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.Xrm.Sdk.IOrganizationService.Execute(OrganizationRequest request)
   at Microsoft.Xrm.Sdk.WebServiceClient.WebProxyClient`1.ExecuteAction[TResult](Func`1 action)
   at Microsoft.Xrm.Tooling.Connector.CrmServiceClient.CrmCommand_Execute(OrganizationRequest req, String errorStringCheck)
======================================================================================================================
Inner Exception Level 1 :
Source  : System.ServiceModel
Method  : ProcessGetResponseWebException
Date    : 17/04/2022
Time    : 19:19:09
Error   : The HTTP request to 'https://ipc-qa.crm11.dynamics.com/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.2.47.7698' has exceeded the allotted timeout of 00:02:00. The time allotted to this operation may have been a portion of a longer timeout.
Stack Trace     : at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
======================================================================================================================
Inner Exception Level 2 :
Source  : System
Method  : GetResponse
Date    : 17/04/2022
Time    : 19:19:09
Error   : The operation has timed out
Stack Trace     : at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
======================================================================================================================

[... snip ...]

PackageDeployVerb Error: 2 : Message: MyAmazingSolution - Updating solution Version: 1.0.0.0 to Version : 1.0.0.1 - Deleting Holding Solution FAILED :  : ************ TimeoutException - DeleteAndPromote : Delete and Promote Solution to New version(DeleteAndPromoteSolutionRequest) |=> The request channel timed out while waiting for a reply after 00:01:59.9819968. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
The request channel timed out while waiting for a reply after 00:01:59.9819968. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. => The HTTP request to 'https://myenv.crm11.dynamics.com/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.2.47.7698' has exceeded the allotted timeout of 00:02:00. The time allotted to this operation may have been a portion of a longer timeout. => The operation has timed out[TerminalFailure] Failed to Execute Command - DeleteAndPromote : RequestID=ba768f36-0371-4c6e-b27c-678c8b0b675e : Delete and Promote Solution to New version(DeleteAndPromoteSolutionRequest) duration=00:02:00.0918443 ExceptionMessage = The request channel timed out while waiting for a reply after 00:01:59.9819968. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
The request channel timed out while waiting for a reply after 00:01:59.9819968. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. => The HTTP request to 'https://myenv.crm11.dynamics.com/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.2.47.7698' has exceeded the allotted timeout of 00:02:00. The time allotted to this operation may have been a portion of a longer timeout. => The operation has timed out
Source  : mscorlib
Method  : HandleReturnMessage
Date    : 19:19:09
Time    : 17/04/2022
Error   : The request channel timed out while waiting for a reply after 00:01:59.9819968. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
Stack Trace     : Server stack trace:
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.Xrm.Sdk.IOrganizationService.Execute(OrganizationRequest request)
   at Microsoft.Xrm.Sdk.WebServiceClient.WebProxyClient`1.ExecuteAction[TResult](Func`1 action)
   at Microsoft.Xrm.Tooling.Connector.CrmServiceClient.CrmCommand_Execute(OrganizationRequest req, String errorStringCheck)
======================================================================================================================
Inner Exception Level 1 :
Source  : System.ServiceModel
Method  : ProcessGetResponseWebException
Date    : 19:19:09
Time    : 17/04/2022
Error   : The HTTP request to 'https://myenv.crm11.dynamics.com/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.2.47.7698' has exceeded the allotted timeout of 00:02:00. The time allotted to this operation may have been a portion of a longer timeout.
Stack Trace     : at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
======================================================================================================================
Inner Exception Level 2 :
Source  : System
Method  : GetResponse
Date    : 19:19:09
Time    : 17/04/2022
Error   : The operation has timed out
Stack Trace     : at System.Net.HttpWebRequest.GetResponse()
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
======================================================================================================================
PackageDeployVerb Information: 8 : Message: errorDetails - ErrorCode  - -2146233083
PackageDeployVerb Information: 8 : Message: errorDetails - ErrorName  - NotProvided
PackageDeployVerb Information: 8 : Message: errorDetails - Message  - The request channel timed out while waiting for a reply after 00:01:59.9819968. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
PackageDeployVerb Information: 8 : Message: errorDetails - Type  - Application
PackageDeployVerb Information: 8 : Message: errorDetails - StatusCode  - 500
PackageDeployVerb Information: 8 : Message: errorDetails - Source  - PackageDeployer
PackageDeployVerb Information: 8 : Message: errorDetails - TraceText  - ......Server stack trace: ......   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)......   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)......   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)......   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)......   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)............Exception rethrown at [0]: ......   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)......   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)......   at Microsoft.Xrm.Sdk.IOrganizationService.Execute(OrganizationRequest request)......   at Microsoft.Xrm.Sdk.WebServiceClient.WebProxyClient`1.ExecuteAction[TResult](Func`1 action)......   at Microsoft.Xrm.Tooling.Connector.CrmServiceClient.CrmCommand_Execute(OrganizationRequest req, String errorStringCheck)
PackageDeployVerb Information: 8 : Message: errorDetails - ErrorCode  - -2146233083
PackageDeployVerb Information: 8 : Message: errorDetails - ErrorName  - NotProvided
PackageDeployVerb Information: 8 : Message: errorDetails - Message  - The HTTP request to 'https://myenv.crm11.dynamics.com/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.2.47.7698' has exceeded the allotted timeout of 00:02:00. The time allotted to this operation may have been a portion of a longer timeout.
PackageDeployVerb Information: 8 : Message: errorDetails - Type  - Application
PackageDeployVerb Information: 8 : Message: errorDetails - StatusCode  - 500
PackageDeployVerb Information: 8 : Message: errorDetails - Source  - PackageDeployer
PackageDeployVerb Information: 8 : Message: errorDetails - TraceText  -    at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)......   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)......   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
PackageDeployVerb Information: 8 : Message: errorDetails - ErrorCode  - -2146233079
PackageDeployVerb Information: 8 : Message: errorDetails - ErrorName  - NotProvided
PackageDeployVerb Information: 8 : Message: errorDetails - Message  - The operation has timed out
PackageDeployVerb Information: 8 : Message: errorDetails - Type  - Application
PackageDeployVerb Information: 8 : Message: errorDetails - StatusCode  - 500
PackageDeployVerb Information: 8 : Message: errorDetails - Source  - PackageDeployer
PackageDeployVerb Information: 8 : Message: errorDetails - TraceText  -    at System.Net.HttpWebRequest.GetResponse()......   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
PackageDeployVerb Information: 8 : Message: RaiseFailEvent - update progress with fail event
PackageDeployVerb Information: 8 : Message: ************** BEGIN Queuing UpdateRibbonClientMetadata Job *****************
Beginning queueing up UpdateRibbonClientMetadata job.
PackageDeployVerb Information: 8 : Message: Trying to queue up UpdateRibbonClientMetadata Job.
PackageDeployVerb Information: 8 : Message: Time taken for queuing the ribbon job: 00:00:00.3296308
PackageDeployVerb Information: 8 : Message: ************** UpdateRibbonClientMetadata Job QUEUED *****************
PackageDeployVerb Information: 8 : Message: ****** PACKAGE DEPLOYMENT PROCESS COMPLETED. Result:FAILED  Duration:00:03:19.9664819 ******
PackageDeployVerb Information: 8 : Message: MyAmazingSolution - Pausing for 5 seconds before resuming operation. Retry# 0
Microsoft PowerPlatform CLI
Version: 1.14.2+g7205df7

Error: Updating solution My Amazing Solution version 1.0.0.0 to version 1.0.0.1: Deleting Holding solution.

Usage: pac package deploy [--logFile] [--logConsole] --package

  --logFile                   Log file path (alias: -lf)
  --logConsole                Output log to console (alias: -c)
  --package                   path to a package dll or zip file with a package (alias: -p)

ACTION REQUIRED: Microsoft needs this private repository to complete compliance info

There are open compliance tasks that need to be reviewed for your powerplatform-vscode repo.

Action required: 1 compliance task

To bring this repository to the standard required for 2021, we require administrators of this and all Microsoft GitHub repositories to complete a small set of tasks within the next 60 days. This is critical work to ensure the compliance and security of your microsoft GitHub organization.

Please take a few minutes to complete the task at: https://repos.opensource.microsoft.com/orgs/microsoft/repos/powerplatform-vscode/compliance

• No repository maintainers are set. The Open Source Maintainers are the decision-makers and actionable owners of the repository, irrespective of administrator permission grants on GitHub.

You can close this work item once you have completed the compliance tasks, or it will automatically close within a day of taking action.

If you no longer need this repository, it might be quickest to delete the repo, too.

GitHub inside Microsoft program information

More information about GitHub inside Microsoft and the new GitHub AE product can be found at https://aka.ms/gim or by contacting [email protected]

FYI: current admins at Microsoft include @MattB-msft, @davidjenni, @JimDaly, @lajusp, @MikeStall

"pac paportal list" throws exception

When running command pac paportal list an exception is thrown.

Connected to...Sorry, the app encountered a non recoverable error and will need to terminate. The exception details have been captured and will be forwarded to the development team, if telemetry has been enabled. Exception Id:12afe9c5-d072-4658-aa36-0cec5c53fc9b

• Telemetry is enabled so hopefully there is more details in your logs
• I proceeded to clear the auth list, recreate the auth profile, and try again. No luck.
• I am connecting to Gov cloud, so URLs are of the https://[domain].crm9.dynamics.com variety

`pac admin reset` crashes if currency specified

When the --currency property is specified for the pac admin reset command an error is output, e.g.

PS C:\Dev\XXX> pac admin reset --environment https://myenvurl.crm11.dynamics.com  --currency GBP
Resetting environment...
Microsoft PowerPlatform CLI
Version: 1.14.2+g7205df7

Error: The request failed with error: '{"errors":{"code":"BadRequest","message":"The request does not match the contract","details":[{"code":"BadRequest","message":"The Name field is required.","target":"UnknownTarget"},{"code":"BadRequest","message":"The Symbol field is required.","target":"UnknownTarget"}]}}'. The tracking Id is '51165ec5-08c4-40d8-9a12-ea9f9db9ac83'.

it also occurs when the default USD currency is used

PS C:\Dev\XXX> pac admin reset --environment https://myenvurl.crm11.dynamics.com  --currency USD
Resetting environment...
Microsoft PowerPlatform CLI
Version: 1.14.2+g7205df7

Error: The request failed with error: '{"errors":{"code":"BadRequest","message":"The request does not match the contract","details":[{"code":"BadRequest","message":"The Name field is required.","target":"UnknownTarget"},{"code":"BadRequest","message":"The Symbol field is required.","target":"UnknownTarget"}]}}'. The tracking Id is 'e2017942-c147-49c6-8655-f24bfb3d2b7e'.

Resetting the environment without the --currency flag works, but the currency in the reset environment is always USD.

PS C:\Dev\XXX> pac admin reset --environment https://myenvurl.crm11.dynamics.com                
Resetting environment...
Polling to check the status of your Environment... Execution time: 00:00:05.2646130
Polling to check the status of your Environment... Execution time: 00:00:10.5002040
[... snip ...]
Polling to check the status of your Environment... Execution time: 00:05:19.4620225
Polling to check the status of your Environment... Execution time: 00:05:24.7533558
Polling to check the status of your Environment... Execution time: 00:05:30.2747509
Polling to check the status of your Environment... Execution time: 00:05:35.8037650
Polling completed with status code : OK

 Environment Url                                    Environment Id                           Friendly Name                  Domain Name                    Organization Id                          Version

 https://myenvurl.crm11.dynamics.com/            046d00c3-XXXX-XXXX-XXXX-f0f4a56dfb08     My Env Name                   myenvurl                    9ee5ccab-XXXX-XXXX-XXXX-5281574eabb9     9.2.22034.00148

What does "pac solution version" do?

How and when is the pac solution version command supposed to be used? The documentation on that is very sparse so will appreciate any guidance on that.

`pac auth name` outputs an incorrect error message if name > 30 characters

If a profile is renamed using pac auth name with a new name longer than 30 characters, the error message still says a maximum length of 12 characters, even though the maximum length is now 30 characters.

To reproduce try to rename an existing profile with a name with 31 characters, e.g.

PS C:\Dev\XXXX> pac auth name --index 10 --name 1234567890123456789012345678901
Microsoft PowerPlatform CLI
Version: 1.15.3+g79950a8

Error: Argument --name value is incorrect: The length of the name should be between 1 and 12.

Usage: pac auth name --index --name

  --index                     The index of the profile to be named/renamed (alias: -i)
  --name                      The name you want to give to this authentication profile (maximum 12 characters) (alias: -n)

The error message should say between 1 and 30, and not 1 and 12.

Update to latest version of Power Platform CLI

The latest version of Power Platform CLI showing on Nuget is currently v1.7.4

Does the extension automatically update to the latest version of the CLI?

My terminal window within VSCode seems to still be showing v1.7.2

VSCode extension does not allow renaming of auth profiles > 12 characters

The CLI allows profiles to be renamed up to 30 characters long, whereas the VSCode extension still has input validation which limits the profile length to 12 characters. Occurs in extension version v1.0.9

The problem seems to be here:

powerplatform-vscode/src/client/lib/PacActivityBarUI.ts

Line 72 in 54cda37

validateInput: value => value.length <= 12 ? null : localize("pacCLI.authPanel.nameAuthProfile.validation", 'Maximum 12 characters allowed')

and in the localised error messages

The simple workaround is to use the CLI directly, e.g. pac auth name --index 10 --name 12345678901234567890

Feedback: Option to auto-increment solution version when exporting

I am not sure if there is a way to auto-increment the solution version using pac solution export command. When exporting a solution from the UI, the UI shows an experience where the solution version is automatically set to one higher version.

It will be helpful to be able to do something similar using the CLI. In an ALM strategy where multiple developers are pushing updates to a master solution, the ability to auto-increment the solution version at the time of exporting can be quite useful because with that ability once the solution is exported out and unpacked, it will make it easier to version the solution, check-in to source control and deploy to upstream environments. Please let me know if you would like to discuss for further clarity.

Enhancement: Show solution type in 'Environments & Solutions' panel

It would be really useful to have the option of only showing managed/unmanaged/both types of solution within the 'Environments and Solutions' pane.

It would also be really useful to indicate easily (with coloured? padlock? icon) whether each solution was managed/unmanaged in the list

Are you open to pull requests? (if I can work out how to do this !! )

Can't Create CDS Authentication account through PowerApps CLI

Trying to create a CDS --kind Authentication through PAC and gives me this error

Error: Failed to connect to Dataverse
There was no endpoint listening at https://< organization-URL >.crm4.dynamics.com/XRMServices/2011/Organization.svc/web?SDKClientVersion=9.0.46.3082 that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
The remote server returned an error: (407) Proxy Authentication Required.

Our environment is accessing dynamics through a proxy that is installed properly.
I am able to perform other tasks of PAC such as create --kind ADMIN or create a Backup of environment.

In Azure we have an app registration that is pointing at the enterprise application Dynamics CRM and it has user-impersonation with admin consent

Power Apps Portal editing - Liquid in JS is flagged as errors

When you include Liquid tags in javascript when editing a portal advanced form step, the liquid tags cause multiple errors to be displayed:

Add flag to overwrite solution if already exists in the export path during export of solution

Currently if we export solution and if the path already has same file from previous execution, the cli throws an error saying the file already exists. Instead of erroring out it would be nice to add parameter to overwrite existing file.

Repro Steps:

• execute pac solution export --path c:\Users\Documents\SolutionName.zip -- name SolutionName --managed true
• execute same command again
• you will get error message saying the file already exists

Ask:

• Either overwrite by default or add parameter to allow overwriting of file during export, may be something like this:
  pac solution export --path c:\Users\Documents\Solution.zip -- name SampleComponentSolution --managed true --overwrite true

Error running "pac" commands on Apple M1 with dotnet 6.0 arm64 sdk installed

Hi,

The pac commands have started to throw errors on Apple M1 device after installing the arm64 version of the dotnet 6.0 SDK (this is recommended by the release notes of Visual Studio 2022 for Mac Preview 3).

The error being thrown is:

It was not possible to find any compatible framework version
The framework 'Microsoft.NETCore.App', version '5.0.0' (arm64) was not found.
  - The following frameworks were found:
      6.0.0 at [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

You can resolve the problem by installing the specified framework and/or SDK.

The specified framework can be found at:
  - https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=5.0.0&arch=arm64&rid=osx.11.1-arm64
Unhandled exception. Microsoft.PowerPlatform.Tooling.BatchedTelemetry.AppTelemetryException: Telemetry upload process has failed with exit code 150. This usually indicates a deployment configuration issue.
   at Microsoft.PowerPlatform.Tooling.BatchedTelemetry.TelemetryChannel.BatchedTelemetryChannel.ThrowIfUploadProcessHasExitedWithFailure()
   at Microsoft.PowerPlatform.Tooling.BatchedTelemetry.TelemetryChannel.BatchedTelemetryChannel.StartUploadProcess()
   at Microsoft.PowerPlatform.Tooling.BatchedTelemetry.TelemetryChannel.BatchedTelemetryChannel.Flush()
   at Microsoft.PowerPlatform.Tooling.BatchedTelemetry.TelemetryChannel.BatchedTelemetryChannel.Dispose(Boolean disposing)
   at Microsoft.PowerPlatform.Tooling.BatchedTelemetry.TelemetryChannel.BatchedTelemetryChannel.Dispose()
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.Dispose()
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.Dispose()
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.Dispose()
   at bolt.cli.Session.Dispose(Boolean disposing)
   at bolt.cli.Session.Dispose()
   at bolt.Program.Main(String[] args)

Going by the error message, it seems that pac is looking for an arm64 version of dotnet 5.0, which does not exist for macOS, and since that version is not installed it throws an error.

Others have reported similar compatibility issues in the dotnet/installer repo, issue 12187.

A workaround from the issue linked above is to call export DOTNET_ROLL_FORWARD=LatestMajor, which is documented here.

After adding the DOTNET_ROLL_FORWARD workaround, dotnet will look for the latest major version of dotnet installed on the system; which at the moment would be dotnet 6.0 arm64, rather than attempting to find a compatible version of dotnet 5.0.

As an example, running the pac telemetry status command before and after calling the workaround:

---

macOS (Intel and M1) support is mentioned in the blog post announcing the public preview of this extension so this error message may be something other users have encountered also.

'pac solution export' results in access denied error even when running vscode as admin

With the Power Platform VSCode extension installed and successfully connected to a Dataverse environment, I am trying to export a solution by running this command in a VSCode terminal:

pac solution export --path C:\PowerApps\Solutions\SolutionName --name SolutionName -v 1.0.0.0

Which results in this error:

Error: C:\PowerApps\Solutions\SolutionName is an invalid file path. Access to the path 'C:\PowerApps\Solutions\SolutionName' is denied.

I am an admin on the machine and have tried various target directories as well as running VSCode as administrator. All produce the same error.

Extension Version: 1.6.7+g5031575
VSCode Version: 1.56.2

Please use the VSCode language for pac

Even if the windows is not in english (german in my case), a lot of devs prefer all the development tools in english.
We need to do demos in english too.

Unfortunatelly the "Power Platform VS Code extension" gets installed in german. Is there a way to change the language?
Using the VSCode language as a base for the installation would be great too.

Add UniqueName as column when listing environments

It would be very useful to get the uniqueName of the Dataverse environment when executing "pac admin list".

UniqueName has the form of "org*" or "unq*" and is still used in many places. For example when reviewing the installed D365 Marketing applications which have the UniqueName instead of the environment guid.

Error downloading portal via CLI

Hi,

I seem to get the same error regardless of my configuration when attempting to download a portal on an M1 Macbook Air:

I am authenticated via an app registration that is connected to the portal as an Application User.

Any suggestions would be appreciated.

Thank you.

Saved ADMIN profile doesn't work the next day

I created a new admin authentication profile for GCC instance. The admin feature worked after the authentication profile was saved. The next day when i tried to use the same 'ADMIN' profile, i ended up getting the following error message:

*Error: AADSTS70043: The refresh token has expired or is invalid due to sign-in frequency checks by conditional access. The token was issued on 2022-02-01T19:57:21.3802393Z and the maximum allowed lifetime for this request is 86400. *

Since my account uses MFA, i believe whatever token it had saved at the time of creation probably is expired and needs a new token to authenticate. Currently i don't see any option within 'pac admin' module to do that.

Am i supposed to delete my saved ADMIN profile and recreate new ADMIN profile to get the admin feature working again?

Add command to set Environment in Admin mode

Could you please add admin command so that it can set environment to 'Administration' mode. Unless i am not looking in right place, i haven't seen this option anywhere.

It could be something like this:
pac admin config --environment 'environment-url' --admin-mode true
or
pac admin config -env 'environment-url' -am true

Thanks
Sanjeev

"pac paportal download" downloads non adx... table

Hi team,

While downloading a Portal using the CLI, I noticed a non adx table (Note [annotation]) was downloaded together with the rest of the contents.

See below

This presents a challenge for scenarios when a customer wants to download the config of a PROD portal in order to move this to a DEV environment as part of setting up an ALM process.

Could this unexpected behavior be investigated

Extension does not work inside DevContainers

I can install the extension inside a DevContainer with javascript-node:16-buster image, but I cannot run pac inside the bash. I tried with 12-buster - same issue.

`pac solution` commands reach 100% too early

When performing a solution import or export with --async the percentage complete will reach 100 before the platform actually completes the import/export. e.g.

Processing asynchronous request... execution time: 00:06:20.3526315 and 95% complete
Processing asynchronous request... execution time: 00:06:24.3895085 and 96% complete
Processing asynchronous request... execution time: 00:06:28.4275202 and 97% complete
Processing asynchronous request... execution time: 00:06:32.4668427 and 98% complete
Processing asynchronous request... execution time: 00:06:36.5047753 and 99% complete
Processing asynchronous request... execution time: 00:06:40.5428450 and 100% complete
Processing asynchronous request... execution time: 00:06:44.5791273 and 100% complete
Processing asynchronous request... execution time: 00:06:48.6194272 and 100% complete
[ ... snip ... ]
Processing asynchronous request... execution time: 00:07:04.7814496 and 100% complete
Processing asynchronous request... execution time: 00:07:08.8193583 and 100% complete
[ ... snip ... ]
Processing asynchronous request... execution time: 00:10:46.9911967 and 100% complete
Processing asynchronous request... execution time: 00:10:51.0304897 and 100% complete
...

It's a cosmetic issue, and it's been around since --async was introduced. A better approximation of 'completeness' would be reassuring though!

Also, thanks for the continued improvements and developments with pac.

pac paportal upload deploymentProfile duplicating values rather than overriding

This may be user error, but from all the documentation I have read, the deployment profile values are supposed to OVERRIDE the original value. What I see, is it deploys them both, and whatever uses the value doesn't always choose the deployment profile value. I would expect only the value in the deployment profile to be used. Should I delete the original value from the sitesettings.yml file? I didn't see any documentation say to do that.

/portal/deployment-profiles/dev.deployment.yml

adx_sitesetting:
- adx_name: Authentication/OpenIdConnect/AAD-B2C_1/Caption
  adx_sitesettingid: e91069f0-92a4-ec11-983f-000d3a58b83c
  adx_value: Azure AD B2C DEV

/portal/sitesetting.yml:

...
- adx_name: Authentication/OpenIdConnect/AAD-B2C_1/Caption
  adx_sitesettingid: e91069f0-92a4-ec11-983f-000d3a58b83c
  adx_value: Azure AD B2C
...

Command:
pac paportal upload --path "./portal" -dp dev

Values in Portal Management App:

Ennvironment: WSL2, bash, Ubuntu 20.04.4 LTS
Microsoft PowerPlatform CLI
Version: 1.14.2+g7205df7

What does pac solution version

How and when is the pac solution version command supposed to be used? The documentation on that is very sparse so will appreciate any guidance on that.

Add alternate output formats to PAC CLI to enable automated use

PAC CLI output is human readable format, which makes pac difficult to use in other scripts and github actions, e.g.

https://github.com/microsoft/powerplatform-actions/blob/7bbd803800dd4d35eb8d8aa5b132404d25df043d/src/actions/create-environment/index.ts#L27

It would be good to have something along the lines of Azure CLI, e.g. https://www.thomasmaurer.ch/2020/06/how-to-configure-azure-cli-default-output-format/

PLEASE HELP!!! Issues with Power Platform Tools

I recently installed “Power Platform Tools” into Visual Studio Code. I was able to download all of my project files and settings from my portal apps. However, when I am trying to upload the changes that I have made, I am getting this error. “ Updating table adx_webpage with record id:a77ec5d4-9236-ec11-b6e6-00224824282b FAILED due to A validation error occurred. The length of the 'adx_summary' attribute of the 'adx_webpage' entity exceeded the maximum allowed length of '2000'. “

Issue with MacOS and pac

When running the pac command in the terminal (happens both in zsh & pwsh) in VS Code, I get the following error:

To be clear, I have installed .NET core.

Allow publish of specific solution instead of all customization

Currently the cli only allows publish of all customizations of all solutions from the connected instance. i.e.
pac solution publish

It would nice to be able to just publish specific solution from the instance e.g.
pac solution publish [solution name]