Skip to main content

Convert Your Workflow to Power Automate

While creating a new Background Workflow, we all have noticed the below message.
Microsoft Flow( Power Automate) is a growing platform with a variety of new connectors getting added overtime.
However, we all are aware that Workflows have a great capability when it came to including steps like Call Plugins, Workflow Assembly.

And thus, when we think of replacing our existing background Workflows with Microsoft Flows, we might worry about losing our existing Plugin Customization used in Workflow.

So, here are a few easy steps to use all the existing Workflow steps in your Power Automate( Microsoft flow).

Step 1: Create an Action.
Lets take an Example: We had a workflow which triggered on When a Note was created and had the below steps:

The first step Notes Collection, was Workflow assembly that was customized to send history all  notes in a Tabular Format, and was something we wanted to use in Power Automate and so we created the below Action.
The Action has the exact same steps as that of the Workflow.

Step 2: Create a Flow with a trigger same as  your Workflow trigger and call the action.
Once we have created the Action, our goal is to deactivate the Workflow, and call the Action from our power Automate.
To do so, we will add the below step:

This step is in the Common Data Service(current environment) Connector.
Since we have action that belongs to Entity Note, we will create bound action.
If we have a global action, which needs no identifier we can add the step- Perform an unbound Action.

Conclusion: Any Workflow that runs in background and uses Plugins or steps that you would prefer not to change but to use them directly in your Power Automate, then here's an easy way.


Popular posts from this blog

Understanding Dynamics 365 CRM- Part 1

Introduction:In this post I plan to walk you through some concepts and functional aspects of CRM module of Dynamics 365.  We will look into a vast used module of D365 CRM which is Sales in Part 1 of this blog and we shall look into other modules in Part 2
Pre-requisites: Microsoft Office 365 An instance of CRM Dynamics 365/ Trial account.

In Case you don't have a trial account, you can create one on,
For details on how to create an account, Visit my post:
Theory:CRM as we all know is Customer Relationship Management and is majorly used to maintain data with respect to Sales, Customer Tickets, etc.
We have two major parts to understand for working with CRM, Sales and Customer Service. In earlier versions of D365 CRM, we had  three modules Marketing, Sales and Customer Service. The New UI however looks like below:

This new UI as we see does not have marketing Module as it is been no…

Working with Solutions in CRM Dynamics

In this post, we will read about solutions,Components and  Import-Export of solutions in  Dynamics CRM. Also we will see working with both the old and new interface of Dynamics CRM.

Pre- requisites:
An instance of CRM Dynamics 365/ Trial account. Theory:Solutions are used to extend business functionalities in CRM. Solutions provide a framework for packaging, installing, and uninstalling components to match your business functionalities.
Managed and Unmanaged are the two types of solutions.
An unmanaged solution is a solution that is still under development and not intended to be distributed.By default, any new solution is an unmanaged solution and until you have completed all customizations, you must not create a managed solution.
A managed solution is a solution that is completed and intended to be distributed and installed. 
Now since there are many developers working on a project, each one might create different solutions for his/ her part of customizations and there might …