Power Platform Community Forum Thread Details

I want to create a reusable flow like config or logging or exception handling. and the flow can we used accross the multiple projects how it can be done and where the re-usable flows can be stroed and how can be accesses. ( please provide the documents if any)

Categories:

Power Automate Desktop

I am not positive of what you want, but I think I have an idea. For every one of my flows that sends an e-mail, I want to use our company's branding for the look of the e-mails, and I want to include the company logo at the bottom of the e-mail that is a link to the flow that generated the e-mail. With hundreds of flows, this makes it easy to update the CSS or the company logo if it ever changes. I just need to update the one flow, and it is revised for every flow that calls it. If that is what you're looking for, you want to create a child flow, and it needs to be created in a solution.

Any other flow that is also in a solution, will be able to call the child flow. In my example, it is configured this way:

The two variables return the CSS and the image with the link to the parent flow. Flow Link:

CSS variable:

When the child flow is called from the parent, you need to provide the expression for the workflow URL:

You can use this expression:

 
concat(concat(concat('https://make.powerautomate.com/environments/', workflow()?['tags']['environmentName'],'/flows/',workflow()?['name'],'/details')))

Once you understand calling a child flow from another flow, you can do all kinds of things. There is just one thing to note, if you use any actions that require connection references, be sure to update the run only-user setting to use the credentials of the owner of the flow. Otherwise, you'll get a warning when you try to add the Run a child Flow action into your flow. The above flow requires no connection references. And there is an important consideration to keep in mind if you use a flow in this manner. If a connection reference breaks in the child flow, every workflow that calls it will fail. This is why I designed this to use no connection references since it is used by so many flows.

Here is documentation from Microsoft on this concept: Create reusable code with child flows - Power Automate | Microsoft Learn