In this September release we are introducing a new feature (in PREVIEW) for our developers to experience the power of Power Fx. Imagine that as a developer, you need to do a bulk data update to a Dataverse table but you either perform such operation manually or via the user interface. Now you can reduce the time and complexity of your Dataverse operations by using Power Fx from the command line or via a script.<\/p>\n
1. Power-Fx REPL (Read-Evaluate-Print-Loop) command<\/strong><\/p>\n This is an interactive shell for you to try ad-hoc queries, updates, and try different Power Fx expressions.<\/p>\n 2. Power-Fx Run command (using input file mode containing Power Fx logic<\/em>)<\/strong><\/p>\n Here we want to share how a developer can write their Power Fx logic to automate their tasks. \u00a0<\/p>\n command: Here is an example of my file (test.txt) containing Power Fx expression, and the result is shown below.<\/p>\n First, I want to query the first record in the Contacts table to understand the structure. Then I wanted to perform a check for value “a” found in string “asdf” and return “X” if found else “Y” as if I want to use comparisons. Lastly, just decided to query Contacts table for all records where column “fullname” contains “FName”. You can take this example and expand on by adding, deleting, or updating records.<\/p>\n This feature enables developers to use Power Fx formulas to automate their tasks more efficiently.<\/p>\n We would love to hear from you about this Power-Fx capability in CLI and tell us about different scenarios you would like us to include at https:\/\/aka.ms\/pac\/PowerFx<\/a>.<\/p>\n If you find bugs or want to have further discussions, please share them at https:\/\/aka.ms\/PowerFx\/Feedback<\/a>.<\/p>\n In this release we are providing the ability to list your Canvas application in an environment. Now you can do that using the following command:<\/p>\n You can also download the Canvas application as a .msapp file. You will need to provide the name of your Canvas application and you can view additional optional parameters using And there you have it. This was frequently asked for in the issue repository.<\/p>\n In this update, I am happy to announce that we are now providing our professional developers the ability to import data faster into their Power Platform environment by using the NOTE:<\/strong> The data import capability is not available in Power Platform CLI when you install it using dotnet tool, so you will need to use it on Windows within either Visual Studio Code extension or by using the MSI Installer<\/a>. This is because this capability uses .NET framework 4.x.<\/p>\n In the earlier releases, we introduced a way to easily upgrade a solution. Traditionally, you would have to first use In the earlier releases, an administrator could only create up to three (3) developer environments (also known as personal environments). Administrators had limited control because they were only able to provision environments for themselves, and they were concerned about proper adherence to the deployment lifecycle process and governance<\/a>. By keeping administrator control and their concerns in mind, We are now making it easy to govern these developer environments by giving administrators the ability to deploy them on behalf of other users. This can be achieved using the following command, replacing the name of the environment and user as required:<\/p>\n We are so excited to get this release out, we hope you enjoy these new capabilities, and we are looking forward to hearing from you. As you try these capabilities out, please continue to provide your feedback at the following location: https:\/\/aka.ms\/pac\/feedback<\/a>.<\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/powerplatform\/wp-content\/uploads\/sites\/79\/2023\/10\/pfx-1-1.jpg\")
<\/a><\/p>\ncommand: `pac power-fx repl`\n<\/code><\/pre>\n<\/a><\/p>\npac power-fx run --file <File Name><\/code><\/p>\nFirst(Contacts)<\/code><\/p>\nResult = If( Mid( \"asdf\",1,1 ) = \"a\", \"X\", \"Y\" )<\/code><\/p>\nFilter(Contacts, \"FName\" in fullname)<\/code><\/p>\n<\/a><\/p>\nCanvas Application<\/strong><\/h2>\n
pac canvas list<\/code><\/p>\npac canvas download help<\/code> command. In order to download Canvas application you need to use the below command:<\/p>\npac canvas download -- name <App Name or App ID><\/code><\/p>\n<\/a><\/p>\nData import<\/strong><\/h2>\n
--connection-count<\/code> property. If this parameter is not provided, the default connection count is set to 5.<\/p>\n<\/a><\/p>\nSolution Upgrade<\/strong><\/h2>\n
pac solution import --path <solution-zip-file> --import-as-holding<\/code> and then use pac solution upgrade --solution-name <solution-name><\/code>. This update is reducing the number of steps and saving time to upgrade your solution. Now with this improvement, you no longer need to have multiple steps to upgrade your solution, you can simply use below command:<\/p>\npac solution import --path <solution-zip-file> --stage-and-upgrade<\/code><\/p>\n<\/a><\/p>\nCreate an environment on behalf-of<\/strong><\/h2>\n
pac admin create --name \"DevEnvPACCLI\" --type \"Developer\" --user \"snizar@\"contoso.onmicrosoft.com\"<\/code><\/p>\n<\/a><\/p>\n