Power Automate

Bulk Delete has been around since the early days of Dynamics 365. The classic bulk delete interface has a number of limitations. Let’s see if we can use Power Automate to improve on the classic bulk delete.

The three previous posts in this series have examined how to obtain a list of deprecated actions in connectors, so that we can consider migrating to an updated action or alternative connector. In this post I will demonstrate a script that checks power platform solutions for deprecated actions.

In the previous blogs in this series, we created an azure function and custom connector and then updated the function to work more cleanly with the Power Platform. In this blog we’re going to decorate our azure function so that we can more easily create the OpenAPI definition used by the custom connector.

In the last blog we created a durable function and custom connector and used them in a Power Automate Cloud Flow. In this blog, we’re going to update the Azure function to simplify its use within Power Automate - allowing us to use Power Automate’s normal output and error handling.

As the connector ecosystem matures some actions within connectors and perhaps even whole connectors are being deprecated. To avoid unexpected failures it’s useful to know when a connector or action is deprecated so that one can take action, such as migrating to an updated or alternate connector. This first post in a series of blog posts explains how to detect connectors or actions that have been deprecated using an Azure Durable Function and a Power Automate Custom Connector. We’ll extend this in later blog posts to make it more usable.

As noticed by Daniel Laskewitz Microsoft have quietly added the ability to add custom C# code to a power automate connector. Let’s see if it’s possible to speed up our prime number calculation using this new functionality and if so what kind of performance improvement is possible.