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.
Did you know that Dataverse will check if a string field is a date and try to truncate it before it saves it? Neither did I until today.
Windows Workflow Foundation (WWF) is the long-serving underpinning of multiple solution components within Dynamics 365 and the Power Platform. With the announcement of Power Fx, it’s clear that Microsoft will consolidate on a single expression language and eventually remove the dependency on WWF.
Let’s review the solution components that use WWF and consider how to develop complex solutions in anticipation of the impact of Power Fx.
A recent update to the solution engine means we now have fewer merge conflicts due to a change in the critical
solution.xml file which makes it easier to implement healthy ALM for Power Platform developments.
We are supposed to be able to uninstall a managed solution when no other solutions or unmanaged layers are dependent on components within the solution that’s being uninstalled - but alas this is not true when calculated fields are used.