Power studio app (previously flow studio) is a great app for Flow makers and administrators. It is offering wide range of options to manage Flows as an administrator. You can use the following functionalities with this app.
Migrate and Deploy
Full Text Search
Export your data
How to use it?
Open this link and sign in with your CDS credentials.
You can see list of Flows with multiple operations like Export Excel, Flow Diagram, Sort, Filter and etc.,
Click on (…) next to any flow for more operations. You can see all operations that you can perform on each Flow in the below screen shot.
They are offering one month trail version, so I suggest everyone to subscribe for trail version and explore all the options. I like the Flow Diagram and Snapshots options the most.
Sometimes we need to perform set of operations as a transaction which means if one operation fails in a set of operations, we have to roll back all the operations in that transaction. For example, in your Flow you are creating a record followed by update record, it is necessary that both of these operations should complete successfully otherwise you should not run any of them. Now, you can do such things using Changeset control of MS Flow.
As of now, you can perform Create, Update and Delete operations only (CDS) in Changeset request.
Note: Common Data Service(Current Environment) is visible only when you create a Flow inside a solution.
Now you can use Scope to restrict the execution of power automate (Flow). This functionality works exactly like the Scope filed on OOB Workflow. For ex: if you select “BusinessUnit” as a Scope for any of your power automate, it will trigger for all users of the same business unit of the context user.
Power Automate extending it’s functionality day by day, isn’t it?
Recently I worked on one project where I integrated the contacts and groups from SharePoint to Exchange Online. I want to share the approach that I followed to do this.
I used PowerShell scripts to create objects (Contacts and Groups) in Exchange Online. Initially, I thought of using Azure Functions with C#, but it’s not possible as there is no API exposed for Exchange Online. I used MS Flow to trigger my PowerShell scripts that I have developed in Runbooks (Azure Automation) on Create/Update of sharepoint list item. We have an action in Flow to create a job of a particular Runbook (Azure Automation –> Create job).
The reason to use MS Flow for this requirement is to develop an application with low-code which facilitates the customer to perform some basic changes without need of a developer.
In one of my previous blog I mentioned how to use on demand flow within MS CRM. But we have some limitations with that approach
we can’t apply Enable rules on the Flow button as it is OOB context menu which generates dynamically based on the number of flows.
we can’t restrict a call to Flow to check the conditions whether Flow needs to run or not, I mean we can’t apply our conditions before a request goes to Flow.
Step 1: Create a Flow with HTTP Request with proper “Request Body JSON schema” (use sample payload option to generate the schema)
Step 2: Add “Create a new record (Dynamics)” action to create a new Contact in CRM.
Step 3: Add a Response action at the end to send the response back to CRM and Save the Flow .
Step 5: Create a ribbon button in CRM and call the below function from the ribbon button.
with this approach you can add all your validations in the java script and call the Flow once the conditions met, this way we can reduce lot of unnecessary calls to Flow. We can pass whole record context to Flow if needed. Hope it is interesting 🙂
We all know that dialogs should be replaced with either BPF or Canvas App as dialogs were deprecated in Dynamics 365 CE, but what if we want a simple dialog which will accept some custom parameters and use those values to process the business logic? The best alternative for this scenario is MS Flows. We can create a Flow and call explicitly from “Flow” button on the CRM record. For this, we need to create a Flow with the trigger “Common Data Service –> When the record is selected”. Take an example to convert a lead to opportunity based on some parameters. The below is the Flow that I developed.
After the Flow creation, you can see this Flow from the Lead entity records like below.
The Flow will open the dialog like below with set of questions that we defined above once you click on “Qualify Lead” button.
Click on “Run Flow” button to execute the Flow
Your flow executed successfully and created an opportunity record.
With this, we can create simple dialogs very easily with out any extra efforts. Hope this will be useful for other developers.
Today we got a requirement to fetch all the records that are created in the last month by using MS Flow. We can do this by using “Dynamics 365 List records” action and we have to provide OData filter query for this action. I tried to use the same “last-month” operator that we use in the fetch xml. But this will not work for OData query. We need to use “LastMonth” function for this as defined in this link. The below are the examples to use these date functions.