In our previous release of Power Platform CLI, we had shared updates related to the A developer can use below command to download Canvas .msapp file and extract the .msapp file into a chosen directory to take a peek at the artifacts.<\/p>\n Please do note that Why, because when we use We heard from number of our community members for having an alias to use when invoking Power Fx capability. Now, instead of typing We have also updated our documentation<\/a> to share what Power Fx functionality can be used in Power Fx capability within Power Platform CLI. This updated link is now available within REPL when used “Help()” function.<\/p>\n We have listed the link at the bottom of the function list (see in the below image): A specific REPL function list https:\/\/aka.ms\/Power-Fx-PAC-CLI<\/em>\u00a0<\/p>\n Don’t forget to review our functions list as we are constantly adding support for additional Power Fx functions into this capability within Power Platform CLI.<\/p>\n Power Platform CLI should be auto upgrading the token cache to the new format, so there should not be a mismatch. However, there is an edge case, that is:<\/p>\n Thinking of security improvements within Power Platform CLI, we are now providing additional features of utilizing Prior to this improvement, if your import had failed there was no details provided where one could easily look for an error. Now we have made an update so that the process will return a non-zero return code if an import fails. This will helps speed up the resolution of the failure.<\/p>\n We are happy to share that we are now supporting long path names in Power Platform CLI on Windows. For instance, when working with solutions, you might have a long path name where your solution is stored, such as pac solution clone<\/strong>, one can use a long path name (path limitations<\/a>).<\/p>\n I want to note here that in order to use the package deployer, it is required that one must have the Full .NET Framework version of the Power Platform CLI where “Full .NET Framework” implies that it’s Windows only.<\/p>\n We have added a new You can use below command to utilize the Now for this update, we have been hearing requests from our developer community for this improvement when creating an environment, they want to be able to use a security group. Now you can do that by simply providing the Microsoft Entra ID Security Group when using Please note that the security group ID must be a valid GUID.<\/p>\n You can get you security group id from Azure portal but going to Azure Active Directory (Microsoft Entra ID) –> select With the addition of Let me not forget about Imagine you have an application, model-driven application in this case, and you want to alter roles for this application that is an administration operation, but you are not able to do so from the Power Platform CLI because you have not registered this application and is not visible in the list. First you will need to get the application ID, which you can get the application ID from the UI or the link (highlighted below).<\/p>\n What commands are available with Now, you would need to use below command to register the application using the application ID from previous step. When you list the application using Once we no longer have a need for the application, we can unregister the application and it will be removed from the list of applications where an administration operation can be performed. We use below command to unregister and upon unregistering, you can see that it will disappear from the list below.<\/p>\n Now we are happy to share that you can register and unregister application right from the Power Platform CLI by using one of the below commands and feel free to visit our documentation<\/a> on these.<\/p>\n For our developers using Power Virtual Agent bots<\/strong> and want to manage their bots via Power Platform CLI, we have added the ability to extract & merge files with localized content and the ability to extract a template file from an existing bot assuming the bot is part of an environment. Here is a link to our documentation<\/a> for additional arguments to be used.<\/p>\n To demonstrate the ability, I created a sample bot in my developer environment. Below I am going to share by listing the bots in my environment that I am connected to. I will then use below command to extract a template file from the bot I created.<\/p>\n Below commands can be used to extract and\/or merge files with localized contents.<\/p>\n We are so excited to get these updates rolled out, we hope you enjoy these new updates, and we are looking forward to hearing from you. As you try out these updates, please continue to provide your feedback at the following location: https:\/\/aka.ms\/pac\/feedback<\/a>.<\/p>\npac canvas list<\/code> and pac canvas download<\/code> for your .msapp file. We are continuing to improve this process but now having an additional property --extract-to-directory<\/code> to extract your .msapp file (Canvas application) to a specific folder.<\/p>\npac canvas download --name <canvas_app> --extract-to-directory <destination_folder>\n<\/code><\/pre>\n--extract-to-directory<\/code> argument is not to be confused with pac canvas unpack<\/code> functionality.<\/p>\n--extract-to-directory<\/code> argument, it will automatically extract the .msapp file to look at the raw artifacts but when we use pac canvas unpack<\/code>, where pack\/unpack are preview\/experimental commands<\/strong>, we will convert to an alternate format<\/a>. Now, look at the image below where we have extracted the .msapp file.<\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/powerplatform\/wp-content\/uploads\/sites\/79\/2023\/12\/canvas-download.png\")
<\/a><\/p>\nPower Fx capability with an alias<\/strong><\/h2>\n
pac power-fx repl<\/code>, you can simply use pac pfx repl<\/code>.<\/p>\n![\"Power-Fx](\"https:\/\/devblogs.microsoft.com\/powerplatform\/wp-content\/uploads\/sites\/79\/2023\/12\/pfx-1.png\")
<\/a><\/p>\nSecurity
Token Cache<\/code> improvement in pac auth<\/code><\/strong><\/h2>\n\n
Token Cache<\/code> with “pac auth”. If you want to learn more about authentication profiles, check this<\/a> post.<\/p>\nUpdate into
data import<\/code> capability<\/strong><\/h2>\nLong path names support<\/strong><\/h2>\n
pac solution clone --name MMC_test --outputDirectory \"\\\\?\\c:\\Very_Long_Path\"\n<\/code><\/pre>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/powerplatform\/wp-content\/uploads\/sites\/79\/2023\/12\/LongPathNames-2.png\")
<\/a><\/p>\nPackage deployer using
--solution<\/code> argument<\/strong><\/h2>\n--solution<\/code> argument which adds the ability to pass a solution to package deployer to deploy the solution. This will allow the package deployer processor to support async, retry, timeout and other features that it uses to deliver a solution to an environment.<\/p>\n--solution<\/code> argument.<\/p>\npac package deploy --solution SolutionFile.zip\n<\/code><\/pre>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/powerplatform\/wp-content\/uploads\/sites\/79\/2023\/12\/package-deploy-1.png\")
<\/a><\/p>\nSecurity Group ID in
pac admin create<\/code> using --security-group-id<\/code><\/strong><\/h2>\npac admin create<\/code> with a --security-group-id<\/code> property.<\/p>\nGroups<\/code> in the left blade, you will see the screen below.<\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/powerplatform\/wp-content\/uploads\/sites\/79\/2023\/12\/GUID.png\")
<\/a><\/p>\nUsing Unique solution name in
pac pcf push<\/code> with --solution-unique-name<\/code><\/strong><\/h2>\n--solution-unique-name<\/code> argument (mutually exclusive with --publisher-prefix<\/code> argument), one can now add the component using the unique name of the solution. When using the target environment, which is now supported, the temporary solution (and the temporary publisher) and the publisher prefix from the target environment will be deleted after an import is successful. You can get the solution unique name by using the pac solution list<\/code> command and the first column in the output is the unique name (see below).<\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/powerplatform\/wp-content\/uploads\/sites\/79\/2023\/12\/solution-unique-name.png\")
<\/a><\/p>\nAdmin capabilities for application register and unregister<\/strong><\/h2>\n
pac admin application register<\/code> and pac admin application unregister<\/code>. Previously one would have to use PowerShell to register applications and there was no command line option to unregister.<\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/powerplatform\/wp-content\/uploads\/sites\/79\/2023\/12\/AppRegUnreg.png\")
<\/a><\/p>\npac admin application<\/code>, well you can list, register, and unregister applications for your tenant, that are.<\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/powerplatform\/wp-content\/uploads\/sites\/79\/2023\/12\/AppRegUnreg-2.png\")
<\/a><\/p>\npac admin application list<\/code>, you are not seeing the application ID in the list. After you run below register command, and then list the application, you will see the application ID in the list.<\/p>\npac admin application register --application-id <application_id>\n<\/code><\/pre>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/powerplatform\/wp-content\/uploads\/sites\/79\/2023\/12\/AppRegUnreg-3.png\")
<\/a><\/p>\npac admin application unregister --application-id <application_id>\n<\/code><\/pre>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/powerplatform\/wp-content\/uploads\/sites\/79\/2023\/12\/AppRegUnreg-4.png\")
<\/a><\/p>\npac admin application register --application-id <application_id>\n\npac admin application unregister --application-id <application_id>\n<\/code><\/pre>\nPower Virtual Agent bots updates (recently renamed to Microsoft Copilot Studio)<\/strong><\/h2>\n
pac virtual-agent extract-template --bot <Chatbot_ID> --templateFileName <YAML_template_file> \n<\/code><\/pre>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/powerplatform\/wp-content\/uploads\/sites\/79\/2023\/12\/pva-2.png\")
<\/a><\/p>\n![\"Details\"](\"https:\/\/devblogs.microsoft.com\/powerplatform\/wp-content\/uploads\/sites\/79\/2023\/12\/pva-1.png\")
<\/a><\/p>\n