10/30/2023 0 Comments Desktop flow power automateOnce we have selected it, we can click on the Next button to proceed. We now need to browse for our solution package. We can now change our environment to our Test environment (or equivalent) and choose to Import our zip file. We want to make a note of where this zip file is located. For more info on Connection Reference, please watch this YouTube video.Ī zip file that contains our solution will now be available. Where possible you should use Connection References which allows you to establish connections from outside the workflow editor when using Managed solutions. Now we can go ahead and export our solution by clicking on Export button.ĭepending upon your scenario, select Managed or Unmanaged as your solution type. If you know that you are going to be transporting your flows, it is recommended to start directly building in a solution. Note: You can also create new flows from within a solution by clicking on the New dropdown. Once we have done so, we can use the Add existing dropdown to select both our Cloud flow (Call Desktop flow) and then UI Flow (My Shared Flow). Desktop flows are “solution aware” which means they can be included in Dataverse Solutions, which allows us to take advantage of that transport mechanism.įirst, we will create a solution and provide it with a name. But how can we copy/move a flow from our Dev environment into our Test environment? The answer is Solutions. Now that Power Automate Desktop has reached general availability, organizations are looking to include Power Automate Desktop flows in their deployment processes and move them from one environment to another environment.Īs we have seen in other tips, we do have an environment picker that is available in Power Automate Desktop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |