Skip to main content

Develop and Deploy Microsoft Flow Applications


Development and deployment of Microsoft Applications has never been easy. In actual production environments you need to develop your application, test it, release to UAT and ultimately release to the live environment.

Microsoft Flow’s Export and Import functions made this process convenient and easy.
First you need to create your Flow in your development environment.
I have few sample scenarios.

Scenario one


Assume that you are having support email address on Gmail and you want to create a follow up task to the supporting team which is on the Microsoft Outlook environment.

Scenario two

 Assume that your sales team need an approval of a customer document. In generally sales team need to scan the document and send to the relevant person via email and get the approval. Here you can use your Flow mobile application to trigger the process.

After Finalizing your Flow,

Export Process


Then go to My Flow






Where you can see all your business flows
Select the automation flow that you need to export.


And then select the Export as Package Zip.
Then you will see a Form like below, which you should understand properly.




First section is how to deal with the import operation.



There are two options available.

  • ·       Create a New Flow on your destination
  • ·       Update the existing Flow on your destination





You can choose the preference approach.

Second part is all about the connectors.  You might have different connections for your dev, staging and production.  Before importing the Solution you should create the connection in your production environment, if it is not exists.

Connections need to select when you are importing the zip. Please refer Import Process




Import Process

Creating Connectors
Click on connectors on your production



Here you can see all your existing connectors in the environment.  You can add new connections if it is not exists.

Then go to My Flows and click on Import link


There you can import the zip package where you exported before.



Now you can select the Update and select the existing Flow to update. Then click on Select during import and select existing connection.




  

Comments

Popular posts from this blog

How to Link Two List and Create a combine view in the SharePoint 2010

In this way you can join multiple list together and can create a combine view. for an example assume that you are managing a list for some events. And also you are having a participants in separate list. Thus you want to join the two list and create a composite view. SharePoint 2010 allows you to create this kind of view using  Linked Data Source. in this approach you can create your own custom list in the SharePoint. How to Create a Linked Data source Go to SharePoint designer and  go to the link called data sources. And Click the Linked Data Source button in the ribbon. Then SharePoint designer will prompt following kind of a dialog. In there add two list, that you wan to linked together. I'm adding airline schedule and booking list. those are the two list that i wan to merge. then click next. And it will guide you another screen. it will ask you to select either Merge Merge use to combine list which are having same columns definition. for and example we can say th

Motion Eye Docker compose File

Docker compose files are comes in handy when considering container orchestration. Below example shows my docker compose files and folder structure. ---- Your Folder (motioneye)   -- etc   -- lib   -- docker-compose.yaml You can run the docker compose file using docker-compose -d , and etc and lib folder will be automatically populated in the initiation. --- Below shows the content of the docker-compose.yaml file. version: '3' services:   nodered:    image: "ccrisan/motioneye:master-amd64"    container_name: motioneye    restart: always    user: root    ports:      - 8765:8765    volumes:      - "/etc/localtime:/etc/localtime:ro"      - "./etc:/etc/motioneye"      - "./lib:/var/lib/motioneye"

How to get Username , UserID in CAML Query

If you are want to get the userID you can simple use following code. <Where>    <Eq>       <FieldRef Name='userfieldname' />       <Value Type='Integer'>            <UserID Type='Integer' />       </Value>    </Eq> </Where> in here you should declare the UserID variable before it uses. normally If you make a user filter in the SharePoint designer it will automatically create the parameter in parameter binding section in the web part. <ParameterBinding Name="UserID" Location="CAMLVariable" DefaultValue="CurrentUserName"/> But assume you want to filter using a user name and the field is not a persongroup feild and it is just a text field. then you can use following query to archive it. <Where>    <Eq>       <FieldRef Name='userfieldname' />       <Value Type=’Text’>            <UserID Type=’Text’/>       </Value>    </Eq> </Wh