Exporting Microsoft Flow From One Environment And Importing To Another

If you’ve jumped onto the Microsoft Flow bandwagon, you know already how easy it is to create them. Did you know that you can also export them from one environment, and import them into another? The process is straightforward (As it should be!) but there are a few things you need to keep in mind to make the export and import successful.

First, let’s look at the two environments. In the environment below (let’s call it Environment A), I want to export the first Flow into a different environment, where it doesn’t exist yet.

The second environment (let’s call it Environment B), where it needs to be imported, looks like this (sans the RSS/LinkedIn Flow).

Now, in order to export from A, we will click on the three ellipses on the desired Flow, click Export, and choose Package (.zip).

You would think that selecting that option just downloads a .zip file for you. Instead, it brings you to a different screen where you give the package a name, and an optional description. At the bottom, notice the “Import Setup” column.

The Import Setup for the Flow defaults to Update. What it means is that it assumes this Flow exists in Environment B already, and that it will just update it with any changes it may have. Click Update, and choose “Create as new” so that a new Flow is created in B. Click Save to exit the screen. Finally click Export to download the .zip package file.

 

Export DONE.

Now, go to Environment B. Go to My Flows, and click “Import”, and upload the .zip package.

Here, notice the red ! next to the Flow and connectors required. Even though in our Export process, we had setup the “Import Setup” to Create New, it still defaults to Update. Click Update, change this to “Create New”, and Save. Now notice the red ! disappear.

For the connectors, click on them one by one. If a Connector exists already, it will show it to you in a list from where you select it. If it doesn’t exist, it will ask you to create it (by clicking “Create new”).

After you click Save, and take care of the Red ! for the connectors, click Import. A successful import shows the following screen with green check marks.

After the import is done, you will see the new Flow in your new environment, already turned on!

Create Records In CRM For Dynamics 365 By Pressing A Physical Button! (Using Flic & Microsoft Flow)

What if your customers could just literally press a button to solve their problems? Picture the following scenarios:

– Your clients, who use your products or services, are having trouble with them. Something’s not right! They press a button and immediately get a call from your support staff.

– You run a coffee shop or a restaurant. You notice that you are low on supplies (Coffee beans? Beverages? Ketchup?). You press a button which sends an email to your supplier telling them to restock supplies.

– You run a roofing company. Your staff is up on one of the roofs fixing things. Once they are done, they press a button that creates a record in CRM, notifying office staff that the job has been completed.

That would be pretty awesome, right? (no? aww okay :/)

In case you didn’t know, Microsoft Flow can now be triggered by “Flic” – a physical button that connects to various services like Uber (to order a cab), Sonos (to control music), and Philips Hue (to control smart bulbs) to name just a few.

With Flic now working with Microsoft Flow, we can use this combination to create records in CRM for Dynamics 365, and perform various actions. For example, in the video below, I show how a customer, whenever they have an issue with our product or service, can just press Flic once, which will create a case record in our CRM.

Benefits

So what are some benefits of automation tools like Microsoft Flow, especially when they are combined with smart buttons like Flic?
  1. It makes initiating a process or action much easier and convenient.
  2. It encourages people to follow the process because everything is already automated.
  3. It brings convenience to your employees with disabilities because just pressing a button performs various tasks for them.

The Flow

This is what my Microsoft Flow looks like. Easy peasy!

Explore:

Flic

Microsoft Flow

Microsoft Dynamics 365