{"id":21283,"date":"2022-08-31T10:38:22","date_gmt":"2022-08-31T17:38:22","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/whats-new-power-apps-august-2022-feature-update\/"},"modified":"2024-10-01T08:33:41","modified_gmt":"2024-10-01T15:33:41","slug":"whats-new-power-apps-august-2022-feature-update","status":"publish","type":"power-apps","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/whats-new-power-apps-august-2022-feature-update\/","title":{"rendered":"What\u2019s new: Power Apps August 2022 Feature Update"},"content":{"rendered":"\n
Welcome to the Power Apps monthly feature update! We will use this blog to share a summary of product, community, and learning updates from throughout the month so you can access it in one easy place. A variety of new and highly anticipated features are now available which we are very excited to share:<\/p>\n\n\n\n
Trust<\/a><\/strong><\/p>\n\n\n\n Maker Productivity<\/a><\/strong><\/p>\n\n\n\n <\/p>\n\n\n\n With the new Power Apps B2B maker preview, working across subsidiaries and partners is easier. Makers can now build apps as a guest in another tenant: apps can be built in the Azure Active Directory tenant it is expected to be hosted. For example, it is now possible for maker@contoso.com<\/a> to build apps directly in the ContosoSubsidiaryA.com tenant.<\/p>\n\n\n\n This reduces the overhead in building and deploying apps in organizations with multiple tenants because of mergers and acquisitions, organizations that use multiple AD tenants for compliance and auditing purposes, e.g. users authenticate in one tenant and access and edit resources in alternate tenants, and organizations that have business partners or contractors working on across tenant boundaries.<\/p>\n\n\n\n Learn more<\/strong> with admin documentation<\/a> and maker documentation<\/a>. <\/p>\n\n\n Two new experimental features are now available for canvas apps connected to Application Insights. The first feature reports unhandled errors experienced by end-users. The second enables correlation tracing across canvas apps and connected custom connectors. Both features can be enabled in the upcoming features menu.<\/p>\n\n\n\n Error reporting will pass unhandled errors during runtime, which end-users experience as a red error banner notification, to Application Insights. Error reporting is a powerful feature that enables trend analysis and proactive alerting on errors experienced by app users. No longer do you have to rely on users to report issues with production apps!<\/p>\n\n\n\n Correlation tracing is a powerful tool to join telemetry events across apps and connected services. Without any added work you can now see outbound requests to custom connectors. For custom connectors that are instrumented with Application Insights, telemetry associated with a call from an app to the connector can be joined to supply a full picture of the call stack. This can be incredibly helpful in debugging issues.<\/p>\n\n\n\n Learn more<\/strong> at Analyze telemetry of a canvas app using Application Insights – Power Apps | Microsoft Docs<\/a><\/p>\n\n\n In 2019, we announced<\/a> the general availability of Solution Checker. This helped many of you analyze your solutions and packages for any issues in your customizations. We got feedback from you that this is very valuable in finding and addressing issues before deploying to production environments.<\/p>\n\n\n\n Today we\u2019re taking a step further and bringing these validations to your development environment to help you find and fix issues in your JavaScript code before being added to a solution. We are excited to announce the public preview of ESLint rules for Power Apps model-driven apps and Dynamics 365 CE.<\/p>\n\n\n\n Learn more<\/strong> at the original blog post<\/a>.<\/p>\n\n\n\n We are excited to announce the release of canvas apps creation as Dataverse solutions by default in public preview. Solutions<\/a> are used to transport apps, flows, tables and other components from one environment to another and are a key mechanism for implementing healthy application lifecycle management (ALM)<\/a> in the Power Platform.<\/p>\n\n\n\n Unlike model-driven apps and most other objects, makers can optionally create their canvas apps outside of a solution and outside Dataverse. This can lead to unhealthy ALM practices, and create an overhead for DevOps teams and admins as they try to automate their ALM process. With this feature, environment admins will be able to set citizen makers and developers in a healthy ALM ready state from day one by enabling canvas apps as Dataverse solutions by default for one or more environments.<\/p>\n\n\n\n Learn more<\/strong> at the original blog post<\/a>.<\/p>\n\n\n\n <\/p>\n\n\n\n We are excited to announce that you can now create new Dataverse tables and edit them using the table designer in the standalone model-driven app designer. This new feature allows you to have a one stop shop for all your table creation and data editing needs by saving you the time it takes moving between designers. <\/p>\n\n\n\n Learn more<\/strong> about how to work-with-model-driven-app-pages<\/a> <\/p>\n\n\n\n And this isn\u2019t limited to just model driven apps! Also, for canvas apps, you can now create and edit Dataverse tables in the current Dataverse environment right from the canvas app designer. You can also add and edit data in those tables right within the canvas studio without leaving the context of your work.<\/p>\n\n\n Ready to get started? Learn more <\/strong>about creating Dataverse tables in the canvas app designer here.<\/a><\/p>\n\n\n\n Custom connectors exist today to be the bridge between Power Platform and Azure Functions (or other REST APIs). But, there are still many manual steps that must be followed to create a functional Power App once a custom connector is in place. The ‘canvas create’ feature of the PAC CLI gives pro developers an easy way to get up and running by letting them automatically generate a functional Power App directly from a custom connector. With this feature, a single command line function will let developers generate a canvas app from their API definition. The app can then be imported into Power Apps Studio for further edits or customization. Makers and developers alike can benefit from the productivity of low code and Power Apps to quickly build rich user experiences over their APIs.<\/p>\n\n\n\n Learn more<\/strong> at the original blog post<\/a>.<\/p>\n\n\n\n The modern command bar is now officially available behind the preview toggle in Settings for canvas page authoring. The new command bar not only has a modern look and feel but is also designed to improve your authoring experience. It allows a seamless customization experience of editing common controls by dynamically displaying the common properties directly within the command bar. This experience can be enabled via \u2018Settings\u2019 under \u2018Upcoming features\u2019 > \u2018Preview\u2019 in canvas web today and will soon be available by default.<\/p>\n\n\n\n Learn more<\/strong> at the docs page<\/a>.<\/p>\n\n\n This capability enables automation of install and update experiences that are offered only through the Power Platform Admin Center experience today. Installs can also be automated for applications available from AppSource provided at least one such install of the said application has been made to another environment within the tenant.<\/p>\n\n\n\n This public API and tools support opens the possibility for Admins and developers to install applications as part of CI\/CD automated processes using their tool of choice. We have enabled this capability directly from Power Platform CLI to ease the onboarding effort for our customers; GitHub and Azure DevOps actions support is forthcoming. Enabling this API and associated tooling addresses a major gap in the Application Lifecycle Management (ALM) story for the Power Platform. We expect significant productivity gains for Pro-developers with this investment; they can now provision Dev, Test and Prod environments and install applications of their choice to those environments before importing their solution(s) ensuring the whole process can be fully automated. In many instances, solutions being developed require pre-requisite applications to be installed already in the target environment; this capability makes this achievable.<\/p>\n\n\n\n Learn more<\/strong> at the original blog post<\/a> and the App Install CLI Command<\/a>, Step-By-Step Tutorial<\/a>, and API Reference<\/a> docs pages.<\/p>\n\n\n <\/p>\n\n\n\n We\u2019ve also released new, and made updates to some of documentation \u2013 see a summary before of some of the key updates :<\/p>\n\n\n\n\n
\n
Trust<\/h2>\n\n\n\n
Build apps across multiple tenants with Azure B2B maker<\/h3>\n\n\n\n
\n\n\n\nImproved app monitoring with experimental Application Insights features<\/a><\/h3>\n\n\n\n
\n\n\n\nESLint rules for Power Apps and Dynamics 365<\/h3>\n\n\n\n
\n\n\n\nCreating canvas apps as Dataverse solutions by default<\/h3>\n\n\n\n
\n\n\n\nMaker Productivity<\/h2>\n\n\n\n
Table designer now in preview in the canvas and model-driven app designers<\/h3>\n\n\n\n
\n
\n
\n\n\n\nAutomatically create a Power App from a REST API<\/h3>\n\n\n\n
\n\n\n\nModern command bar in Canvas<\/h3>\n\n\n\n
\n\n\n\nInstall Apps via Power Platform CLI & Install API<\/h3>\n\n\n\n
\n\n\n\nLearning and Doc Updates<\/h2>\n\n\n\n