Do we need a Dataverse database with Power Automate

  • Do we need a Dataverse database with Power Automate

    Posted by Pierre Poulin on September 22, 2023 at 9:57 am

    Hi,

    All our power automate cloud flows are in our default environment. Which is bad practice. Our flows only connect to M365 and SharePoint at this time. We want to transfer these flows into a unit environment for development and testing and eventually into a production environment. Do these new environments need to have a Dataverse database or can they live without a Dataverse database.

    Thanks

    Jeff Woodard replied 1 year, 1 month ago 2 Members · 1 Reply
  • 1 Reply
  • Jeff Woodard

    Member
    September 22, 2023 at 11:32 am
    Up
    0
    Down
    ::

    Hi Pierre,

    You have to at least have an environment set up for your target location, which I also believe implies there is a dataverse database behind it. We did much of our development before some of the recent ALM features came out in power automate, so we still have some flows in the ‘default’ environment and are still trying to get them all sorted properly. If you’re just starting the process, then it sounds like you first need to create a solution in your default dataverse and move your flows into it. You can use the solutions to group your flows based on functionality / security / however you want to manage them. Once that is in place you can convert your connections to connection references. That’s much handier for testing on a dev database and later moving to production. My advice here is to use as few connections as possible,; the GUI wizards make it entirely too easy to create new connection / connection reference objects instead of re-using existing ones. It’s too easy to create the same connection with the same name, but different guid id which makes things harder later. Also use care in object naming – you want to use your own publisher for the solution so your objects can be named <myid>_<objectname> rather than public_<objectname>. As part of a dev-test-prod lifecycle, you can export the solution from one environment to the next. There are a few references on Microsoft Learn for best practices, here’s a starting point: https://learn.microsoft.com/en-us/power-platform/alm/overview-alm.

The discussion ‘Do we need a Dataverse database with Power Automate’ is closed to new replies.

Start of Discussion
0 of 0 replies June 2018
Now

Welcome to our new site!

Here you will find a wealth of information created for people  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!