{"id":2268,"date":"2020-02-11T23:32:00","date_gmt":"2020-02-12T07:32:00","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/helpful-tips-for-using-child-flows\/"},"modified":"2020-02-11T23:32:00","modified_gmt":"2020-02-12T07:32:00","slug":"helpful-tips-for-using-child-flows","status":"publish","type":"power-automate","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/helpful-tips-for-using-child-flows\/","title":{"rendered":"Helpful tips for using Child Flows"},"content":{"rendered":"
Stephen Siciliano announced Child flows<\/a>\u00a0for Power Automate late last year. His blog also helped flow makers to understand key scenarios for this new feature. We were happy to see so many of you comment on, and show appreciation for this new opportunity.\u00a0 As a result of your feedback, this blog will highlight a few additional best practices and tips for using Child flows. If implemented, they will ensure that you can maximize usage for enterprise scale. I do recommend that you read Stephen’s blog<\/a> firstly, as he sets a solid foundation on the patterns related to this feature, outlines the requirements for usage, and also walks you through your first Child flow tutorial.<\/p>\n We have received feedback asking for additional clarifications on how to pass parameters between the Parent and Child flows. Therefore, we’d like to clarify how this is done today in the scenario below.<\/p>\n EXAMPLE #1 –<\/strong> In this example, there are two SharePoint Online sites which are capturing documentation drafts for different projects. Each library has different work flow processes to drive the submission and authoring of documentation. However, as an enterprise, they have one standardized way to get them approved for posting on their public-facing website. This is a great opportunity to leverage a Child flow which can service multiple libraries, and ensure a consistent process in the whole tenant. I’ve included a video here to illustrate several takeaways for this feature. Can you find at least four takeaways in the video?<\/p>\n <\/p>\n \u00a0<\/p>\nChild flow essentials<\/h2>\n
\n
\n
\n*Please note that manual button flows which are solution-aware may be triggered via a Parent flow. However, they can not be triggered from the Power Automate mobile application. This is a known issue that we are working to resolve (learn more about button flows here<\/a>).<\/li>\n<\/ul>\nPassing parameters from the Parent to the Child flow<\/h2>\n