Maker Deployment page

Makers can now view all their deployments in one place, regardless of solution or pipeline. If their deployment began from (or was deployed to) the current environment, they will be able to view the run history status of it. Failed Deployments and Active Deployments are highlighted in a convenient overview, so you don’t have to go looking for them either!

In addition to deployment visibility, we’ve included a Get started section that will evolve over time. For now, it will link to documentation to help a maker begin their journey to healthy application lifecycle management (ALM).

To further improve understanding of what healthy ALM looks like, we’ll soon be adding recommendations, where makers are alerted to resolve any potentially unhealthy ALM-related behavior, such as housing high-use apps outside of a solution.

Admin Deployment page

The Deployment page in the new admin center provides a streamlined experience to help administrators learn about, setup, and operation best-in-class ALM. The initial preview provides a central location to view all deployments in the tenant, approve deployment requests, and troubleshoot failures.

Select a pipelines host from the picker to see all the pipelines and deployment history managed with that host. A dedicated Failed deployments view helps admins quickly identify and troubleshoot failures and trending issues.

Admins can approve or reject deployment requests assigned to them. First setup Delegated deployments with service principals as the recommended way to deploy securely.

It is important that admins review changes in the solution and the sharing request. With the help of Copilot-generated deployment notes visible in the request, this becomes easier, but if you want a more granular look, be sure to set up Source control integration and link the repository to the approval.

Managed Operations

The Deployment pages are an offering of Managed Operations, allowing all who make or administrate to gain further insight into their Application Lifecycle Management to ensure that business solutions are reliable and performant in production. Aside from just deployment pipelines, these maker and admin experiences will evolve over the coming months and include many more Managed Operations intersections to take advantage of. So, stay tuned for more updates and please leave your feedback below!

Learn more

Admin Deployment page

Maker Deployment page

Managed Operations

New Power Platform Admin Center

The post Introducing Maker and Admin Deployment Pages appeared first on Microsoft Power Platform Blog.

Like with SharePoint, this feature operates with any natively bound gallery where the gallery is directly populated by SharePoint and not by a collection or variable.

Using Copilot with filter

Open a running app that uses a gallery against SQL Server.  If you have a premium license (which is required for the SQL Server connector), then you will see an adorner on your gallery.

Copilot supports three kinds of queries – filter, sort, and search.  While you can type any query you might like, it suggests possible questions based on your data in your app at the time. Note that Copilot over SQL supports an additional verb “in” that SharePoint does not support. It will search for an occurrence of your search text inside of a record value.

Copilot then scopes the records to satisfy the query. It displays a “Filtered” badge in the upper right corner of the gallery.  The exact query that was executed is displayed as a tag. And you can continue to refine your query with additional details by adding more query commands.

Filter, sort, and search galleries with Copilot to filter provides five key benefits:

• Copilot makes end users more productive and saves time. If an author has not built in search and sort capabilities, Copilot enables this scenario and makes them more productive. End users save time with the ability to directly express their query in natural language.
• Copilot saves author’s development time. Authors save time developing apps because they don’t need to develop all the UI controls necessary for the app. Instead, they can rely on Copilot for this functionality.
• Copilot enables queries over the full query result – not just what you can see in the gallery. Users can filter, sort, and search on fields even if the application doesn’t provide UI controls for these tasks. For example, you can search for records even if the application doesn’t have a search bar.
• Copilot is query safe. It only generates queries that can be run on the server. Authors don’t need to worry about whether or not their queries can be delegated.
• Copilot keeps private data private. It only works with the data that is normally returned to the application. It doesn’t access fields that aren’t returned to the app in a gallery/grid or form.

Create a new app with Studio version on or after 3.24092.17 or re-publish an existing app with this version. Then access your app while it is running. (Copilot with filter only appears at runtime, it does not appear inside of Studio.) Select an item in the gallery to start using Copilot with filter.

See the documentation for this feature for more details. https://learn.microsoft.com/en-us/power-apps/user/smartgrid

The post Use Copilot to quickly filter, sort, and search canvas app galleries with SQL Server appeared first on Microsoft Power Platform Blog.

Formula columns are based on Power Fx. Power Fx provides a much richer set of functions than were previously available with calculated columns, especially for text processing and also provides a lowcode way to perform app extensibility.

As you can see in the following Image from Dataverse below , you can use the Power Fx formula bar to create a formula column that computes few arithmetic operations using the supported functions. The formula dynamically returns based on the data type of the resulting expression.

The formula editor supports IntelliSense to suggest formulas and errors in real time.

This feature supports text, decimal, choice, boolean, lookup and limited date/time functionality, targeted primarily for core calculations while we are working towards building the complete parity with existing Calc columns. On read, all calculations are on done on the fly as added projections of the SQL Select query. Results are real time. We are also working on other modes of operation, where values can be calculated and stored on write. This would enable support for rollups of one-to-many and many-to-many relationships, something we are working as part of our future roadmap.

Will this functionality replace existing calculated columns and rollups? Not at present and there will be no rush, those existing technologies are tried and true. Only when we have more feedback and experience, and we’ve worked through any functionality gaps, we will draw up and communicate a long-term migration plan. Eventually we want formula columns should be able to do everything that can be done today, and much more, in an easier to use and Power Platform consistent manner.

Take it for a spin and please let us know what you think! Please leave feedback in the Microsoft Dataverse – Power Platform Community forum. For more details, please refer to our documentation.

The post Boost maker productivity inside Dataverse using formula columns! appeared first on Microsoft Power Platform Blog.