Tip #1291: Do NOT create Flows

I am slowly dragging myself back to reality and going through the backlog of the tips submitted by our readers after an insane family holiday… (You can drop your tip into jar@crmtipoftheday.com. I can’t guarantee that we will publish the tip but I can promise that if we don’t, I will write to you personally explaining why the tip didn’t make it.)

But enough of that. Today’s tip is from Shidin “D365fanboi” Haridas.


Ok, now that I have your attention, let me complete the sentence.

Do NOT create flows unless you are creating it from a CDS solution.

Why??! Because such flows are ‘solution-enabled’ and can be exported and imported during the solution deployment process and hence, better ALM procedures. Woohooo!!!!

Link to documentation: https://flow.microsoft.com/en-us/blog/solutions-in-microsoft-flow/

Screenshot of a Power Maker environment illustrating how to invoke a menu to add a Flow to the solution

Ok, now what to do with the 50+ flows you have already created in your environment?

Don’t worry, here is an easy way to clone your existing flow into a ‘solution-enabled’ flow, courtesy the great Natraj Yegnaraman.

Tîpp Jäår $0.02 + tax

That tip is a good advice if your flow is a part of a PowerApp that includes Common Data Service (CDS). Think of a flow that is, to an extent, a replacement for the legacy workflow.

Besides Flow becoming part of ALM and other mentioned goodness, there is an additional reason to make flow a part of your CDS solution. When you do so, you will have access to Common Data Service (current environment) connector. Why is it cool? Because you will no longer have to deal with reconnecting your flow after the deployment – it will just inherit the current CDS environment the container solution is being deployed into. There is some other goodness in this connector like combined trigger. Plus it’s faster.

Official documentation is now available.

Cover photo by unsplash-logoNicolas Desmangles

5 thoughts on “Tip #1291: Do NOT create Flows

  1. Serf says:

    Is this also possible using Azure Logic Apps?

    • No, Logic Apps cannot be packaged with a solution. That’s one of the areas where Flow provides a better overall experience (as well as the super-duper current environment connector). Logic Apps, on the other hand, provide more control over the deployment, security, scalability, as well as bunch of enterprise connectors like SAP, IBM3270 (gulp!), BizTalk, etc. Usually you would include Logic Apps deployment using ARM templates as part of your ALM cycle.

      The topic is too broad to discuss in details here… I presented Power Platform automation battle: Workflow vs Flow vs Logic App at Sydney and Melbourne DynamicsPower events, perhaps you can contact organisers for a copy.

  2. Matěj Samler says:


    existing flows are now possible to be included in solutions, so you can create Flows from whenever you want.

  3. Linn Zaw Win says:

    Even with Common Data Service (current environment) connector, we still need to authorise the connections one by one (deal with reconnecting the flow) after the deployment, isn’t it?
    Or am I just doing something wrong?

  4. Christian Schulte says:

    You made my day! 🙂
    A possibility to connect to dynamics with an appuser (no MFA) and send mails.
    That’s exactly what I was looking for.

    I had to recreate the flow in the solution to get the CDS (current environment), but after that it worked like a charm. And now I can even specify a select for the queries. Nice.

Leave a Reply

Your email address will not be published. Required fields are marked *