Power Community

Power Community

Welcome to Power Community

Welcome to the latest resources for Dynamics 365 including Customer Engagement, Finance & Operations and Business Central. Every month we deliver free community bootcamp's as well as Microsoft Certification Training Courses. Power Community is the perfect place to launch your career in Dynamics 365 and lead successful digital transformation projects with Microsoft Technologies.


Power platform Developer tools May Refresh

We are delighted to announce the release of our new update (Version: 1.16.5+gba7d6a4) for the Power Platform Command line. This May refresh comes with capabilities ranging from support for single sign-on to even simple things like showing whether solutions are managed or unmanaged when listing out the solutions. So, without further ado, let us get into the details. Single Sign-on (Early Capability) In this new update, when you don’t provide a URL, it creates a universal single sign on authentication profile and authenticates you to your default organization. This is an early single sign-on capability, we plan to improve on it further in the upcoming updates. So, when you use the `pac auth create` command and not provide anything else or `pac auth create -dc` without additional parameters, it will create a new authentication type called universal. You can still authenticate to other dataverse environments, using the –url parameter. But we would really like to get your feedback on this new single sign-on capability. Please let us know what you think. Support for China Sovereign Cloud From PAC CLI we have added support for Azure China Sovereign cloud, this was a long ask from our China based customers and now we can use Power Platform command line capabilities to the China cloud as well. This also means GitHub actions are also supported in the China Sovereign cloud region and eventually we will also support Azure DevOps actions. Here is an example of how you if the China Cloud is supported Support for Packages that hold .cab files We introduced a bunch of new changes to the `pac package` command in the last update, As in now packages can also be build just like a solution, except in packages I can bundle multiple solutions and deploy. Now can you deploy packages that *.cab files Showing if solutions are managed or not on the command line One of the most frequently asked features by our user community by far. We now have the ability at the command line to know if a solution is managed or unmanaged. In the past the only way a user would know if a solution was managed or unmanaged was when they did an export and the export error out saying the solution was managed. Now when you do a `pac solution list`, you get a column identifying whether the solution is managed or unmanaged. As you can see we have been adding more capabilities to the CLI. Our team has been actively working on making our Azure DevOps tasks to also be based on the Power Platform CLI, instead of the current PowerShell modules. We will be pushing out that update in early July, and in most cases those that are using your existing Azure DevOps pipelines should not notice any difference. The benefit of this work is that both GitHub actions and Azure DevOps tasks will be powered by the same engine and be cross platform. As always, we are excited to bring these capabilities to you. If you have additional feedback please reach out to us via the following forums ISVFeedback@Microsoft.com or The PowerUsers community. Raise the issue and bugs at the following location in GitHub https://aka.ms/powerplatform-vscode
- Advertisement -spot_img

Latest News

Announcing the general availability of Power Apps modern commanding

Casey Burke, Senior Program Manager, Thursday, June 2, 2022 We’re very excited to announce modern commanding with Power Fx is now generally available (GA). Modern commanding provides a maker friendly low-code/no-code experience for customizing model-driven app command bars – with the first ever in-product command designer and the ability to use Power Fx (or JavaScript) for expressing business logic. Modern commanding has many improvements since the preview was announced last year. We sincerely appreciate the overwhelming amount of support and feedback from the Power Platform community and the close partnership with Scott Durrow (Microsoft MVP and Ribbon Workbench creator). This has helped shape the below goals and GA features. Makers love the experience A large number of usability and maker productivity improvements have resulted in a simpler and streamlined maker experience. A few highlights include the addition of copy + paste, optimized navigation & layout, drag and drop within command designer, performance improvements, and deferring creation of command component libraries. Do more with Power Fx Various new functions are now available to better support common command use cases. Defining visibility, actions, and interacting with custom pages is now much more powerful. For example, control command visibility using RecordInfo() and DataSourceInfo(), and work with unsaved data (aka the buffer) using Self.Selected.Unsaved. No cliffs Many parity gaps with classic Ribbon commands have been closed (+ a ton of new goodness not previously possible). For example, now you can create dropdowns, split buttons, and groups as well as specify different scopes – which determine whether a command is published to a single app, to a table and all apps using it, or even globally to all apps and all tables. These new scopes prevent duplicating effort for commands that need to be present in multiple apps. As an added benefit, when citizen developers modify or hide broader scoped commands, their changes are automatically isolated within their app and other apps remain unaffected. Rock solid reliability and ALM The most important improvements are not typically visible. We’ve made significant investments into strengthening the modern commanding infrastructure, fixing issues, improving performance and reliability, and ensuring application lifecycle management is handled consistently. GA is a milestone, not an end state. There’s much more we’d like to do and while I can’t share everything just yet, here’s a few improvements coming soon: Editing Microsoft first party (OOB) commands using modern command designer. We realize this limitation is especially painful and have been working diligently to solve this complex problem reliably. Classic OOB commands will be incrementally migrated to the modern commanding infrastructure. Migrated commands will be fully supported in command designer. Migration will not impact existing customer customization or the ability to continue using classic capabilities. We’ll later provide an easy button to migrate your own classic commands. Support for classic enable rules, display rules, and custom rules. Supporting additional Power Fx functions and improving the publishing experience. Addressing other known limitations. Check out the modern commanding documentation as well as the recent Power CAT Live interview with Phil Topness, Prabhat Pandey, and Casey Burke.

Connected Community



Free Training Courses

- Advertisement -spot_img
- Advertisement -spot_img

Video Channel

- Advertisement -spot_img