The Power Platform Center of Excellence Started Kit has historically been a comprehensive reference implementation that demonstrates how to build sophisticated governance, monitoring, and adoption capabilities using Power Platform’s native low-code tools. This collection of components and solutions was there to help develop a strategy for adopting and supporting Power Platform while showcasing what’s possible with the platform’s out-of-the-box features.
In a recent article I wrote about creating a code app and using a Dataverse table to populate data into the code app. In this post, I will go over adding actions, functions and cloud flows and calling them from your code app.
The Power Automate designer had a single User Experience for many years, until about 2 years ago, Microsoft released a new version of the designer with added functionality. You would have to opt in to use the new designer and the flow would allow you to edit it in the Classic or New Interface.
A few days ago Microsoft announced the creation and use of function in Microsoft Dataverse (currently in preview). Functions use Power Fx to execute a set of commands within Dataverse that run on the server-side.
Until now, when working on flows, you were not able to save a flow if there were any errors in it, and would have to fix all the errors before saving the flow, so if you made any changes and needed to save temporarily, you would be stuck
Although this feature might have been out for a couple of months (at least in preview), I recently noticed that the new Dataverse connector (non-legacy), has some new actions that can be performed against other environments, and not only the current environment as was previously named Common Data Services Connector (Current Environment).
While working on a recent project to replace a low code platform with the Power Platform, one of the requirements that we had was to replace some of the Excel export and import functionalities that the existing system had to be able to send large Excel files into various other systems to be analyzed and consumed.
Enterprise transformation programs rarely fail because of technology—they fail due to misalignment across architecture, execution, and governance.
Until recently, if we wanted to call a bound or unbound action from a Canvas app, we would have to create a Power Automate flow that would be triggered from the Canvas App and would then call a bound or unbound action from Power Automate. Not any more…
If you are keeping track of changes in some of the connector actions, you might have noticed recently that Microsoft marked the Send an HTTP request action as deprecated and mentioned to use the Send an HTTP request V2 action instead.
