Skip to main content

Create Power Automate Flow that triggers on Demand, Dynamics 365

 

Create Power Automate Flow that triggers on Demand


Let start by finding When a record is Selected

 


 

Note:- This component belongs to the old Common Data Service, I have noticed you can use it with the new Common Data Service, which is good in my book.

 


For our example here we are going to select Accounts as our Entity, you can enter your environment under Environment, it will take the URL of the environment you are targeting.

If you have any parameters to pass to the Flow you can select any of the following Inputs

  •        Text
  •        Yes/No
  •        File
  •        Email
  •        Number
  •        Date

Text


1.       Add drop-down list options :- will give you the ability to add dropdown values

2.       Add a multi-select list option :- as it name explains it will give you the ability to add multiselect

3.       Mas as Optional :- By default the Text is always required so if you want the Text Imput to be optional you select this one

4.       Delete:- this will remove the Input

 

Yes/No, File, Email, Number, and Date


1.       Make Field required :- it will set the input as required

2.       Delete

Something to Note:-

While working with this component it might look like you have access to every field of the selected Entity, that is quite deceiving, you have access only the Id , User and Input Parameters.

 

For Steps that follow the trigger we can select Components of the new common Data service


 

To access the Account Id you can use the following Expression

triggerBody()?[‘entity’]?[‘Field Name’]

for this scenario

triggerBody()?[‘entity’]?[‘accountid’]


You will be able to access the Flow from the View or the Form 

 

 

 

 

Comments

Popular posts from this blog

Azure DevOps Fork Repos between two Organization

  Azure DevOps Fork Repos between two Organization This weekend I embarked on a topic a bit foreign to myself, on the surface seemed a bit simple. The idea is to fork my Azure DevOps Repo to a different organization and push changes between them. Bad news DevOps doesn’t allow to fork Repos to a different organization, you have only the capability to fork to a different Projects within the same Organization. I’m pretty much sure there are so many other ways to solve this issue, but this is the one that I found to be easy to implement. Import Repo to the new Organization Remember here you have to generate a personal token to be able to import the Repo you have to be a member of the new organization as well This might take a few minutes depending on the size of your project, once its complete you will receive a confirmation email, or just refresh it after few minutes So far all looks good, you can clone the solution in your new Organization,

Power Platform Tool for Visual Studio 2019/2022

 Power Platform Tool for Visual Studio 2019/2022 We have a new Visual Studio Extension Power Platform Tool.  Creation and deployment of Plugins, Custom Workflows and WebResources is going to be easy and time saving.  This article is going to focus on how to connect to your environment and create your Visual Studio Solution. In a subsequent article I will try to cover on how to Create and deploy your components to your environment. Installation is straight forward go to      Tools→ Manage Extensions→ Search for Power Platform Tools     You will Need Visual Studio 2019 or later version     Subsciption to Pawer App/Dataverse or trial       .Net Framework 4.6.2 Now we will go over how to create a Project and connect it to your Environment Open Visual Studio 2019 →New Project Search for Power Platform Solution Template Add Project Name and Location → Create Click on Start from Dataverse to connect to your environment Enter the following and → Login

How to use Formatted Values in Power Automate Flow Dynamics 365

  How to use Formatted Values in Power Automate Flow Dynamics 365   If you have been working on Power Automate for Dynamics 365 you might have been wandering how you can access a lookup Formatted Value or Option Set formatted values. You can use the following format to access: body(‘{Action Name}’)?[‘{fieldname} @OData.Community.Display.V1. FormattedValue’] You just have to be mindful in Dynamics 365 lookup field name they do not translate to the proper field name, you might have to and an “_” as a prefix and “_value” as a postfix, I will leave that to you.