Category: Power Platform

This post is part of the New Functionality In Microsoft Power Automate 2024 Wave 1 series in which I am taking a look at the new functionality introduced in Microsoft Power Automate 2024 Wave 1.

The 5th of the new functionality in the Cloud Flows section is connect to other environments from the Microsoft Dataverse connector.

Users can create flows that combine data and perform operations across different Microsoft Dataverse databases.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview:  Nov 12, 2023
Early Access: –
General Availability: Apr 2024

Feature Details

Currently, you must use the Microsoft Dataverse (legacy) connector to connect to environments outside of the current environment. With this feature, you can connect to other environments from the Microsoft Dataverse connector’s actions and triggers

My Opinion

In order to judge this enhancement, I need to get more up to speed on the Dataverse and specifically how it interacts with Business Central, as most of my work is with that ERP and the flows I create interact with it in some way.

This post is part of the New Functionality In Microsoft Power Automate 2024 Wave 1 series in which I am taking a look at the new functionality introduced in Microsoft Power Automate 2024 Wave 1.

The 4th of the new functionality in the Cloud Flows section is monitor performance for cloud and desktop flow activities.

You can use a central consolidated view to monitor and understand the executions across cloud and desktop flows.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: May 2024
Early Access: –
General Availability: –

Feature Details

With this feature, you have a single consolidated view to understand the automation performance across your cloud and desktop flows. This feature enables you to:

• Understand the top trends across all of your automation assets (for example, success and failure) across different time periods.
• Understand top errors and their trends.
• Understand top flows with specific errors.
• Seamlessly switch between cloud and desktop flows activity.

My Opinion

This looks to be a good enhancement to monitoring which will allow you to see if any flows are problematic.

This article is part of the Working with Power Automate Child Flows series and of the larger Working with Power Automate series I am writing on my experiences working with the Power Automate, which is part of the Power Platform from Microsoft. I also have a related series of articles on Power Automate with Microsoft Dynamics 365 BC.

If you create a child flow and call it from a parent, you may receive this error:

However, you will only be receiving the error if you have missed a step when creating the child flow; you need to change the run-only users setting, which I covered in this article.

This article is part of the Working with Power Automate Child Flows series and of the larger Working with Power Automate series I am writing on my experiences working with the Power Automate, which is part of the Power Platform from Microsoft. I also have a related series of articles on Power Automate with Microsoft Dynamics 365 BC.

With the child and parent flow examples created, they can now be tested. As the example parent flow, is an instant flow, to run the flow, go to the My flows page, select the parent flow in the list and click the button:

Continue reading “Working with Power Automate Child Flows: Test the Parent/Child Flow Examples”

This article is part of the Working with Power Automate Child Flows series and of the larger Working with Power Automate series I am writing on my experiences working with the Power Automate, which is part of the Power Platform from Microsoft. I also have a related series of articles on Power Automate with Microsoft Dynamics 365 BC.

With the child flow created and the run-only users setting changed, we can add the child flow to parent flows. In this article, I am going to create an example flow which prompts the user for a message which is passed into the child flow and then receives back and emails an output message from the child flow.

The parent calling a child flow, can be any type of flow, but for this example, I am creating an instant cloud flow. Do this by opening your solution and clicking New » Automation » Cloud flow » Instant:

Continue reading “Working with Power Automate Child Flows: Add a Child Flow To a Parent Flow”

This article is part of the Working with Power Automate Child Flows series and of the larger Working with Power Automate series I am writing on my experiences working with the Power Automate, which is part of the Power Platform from Microsoft. I also have a related series of articles on Power Automate with Microsoft Dynamics 365 BC.

After creating a child flow, there is one setting in the flow which needs to be set. This is to change the Run only users setting. Do this, by opening the flow to see the details and clicking the Edit button in the Run only users box in the lower right corner of the page:

Continue reading “Working with Power Automate Child Flows: Change Run Only Users For Child Flow”

This article is part of the Working with Power Automate Child Flows series and of the larger Working with Power Automate series I am writing on my experiences working with the Power Automate, which is part of the Power Platform from Microsoft. I also have a related series of articles on Power Automate with Microsoft Dynamics 365 BC.

Child flows in Power Automate are quite easy to create and there is actually very little difference between creating a child flow and a normal flow; the main difference is actually in the final step of the child flow. In this example, I’m going to create a simple child flow, including a step to send an email, just to show a complete flow.

Child flows are created as instant cloud flows. To create a child flow, open your solution and click New » Automation » Cloud flow » Instant:

Continue reading “Working with Power Automate Child Flows: Create a Child Flow”