Ever wondered how to call an Action from a Flow using the new Common Data Service (Current Environment) connector? There are 2 actions to perform this –
Here’s a quick post to demonstrate that and the difference between Perform a bound action and Perform an unbound action in the CDS (Current Environment) connector.
Note that the connector used here is Common Data Service (Current Environment) connector which is available only if you are creating a Flow inside a Solution, not outside.
Check more on this connector here – Selecting (Current) in Environment in Power Automate CDS connector and why it matters
Bound Action meaning calling an Action in Dynamics 365 that is bound to any one entity i.e. which is not a Global Action
- In this example. I’m creating a Flow that will call a Bound Action which runs on Account entity.
- And the InputName field shown above will simply take a string field and reflect the same as it is in Output
- Now, I am using Perform a bound action Action from the Common Data Service (Current Environment) connector as shown below-
- Once you select Perform a bound action, you’ll need to select what entity the Action is tied to with the following properties –
Entity Name: Name of the entity the Action is bound to
Action Name: Name of the action (not Display Name)
Item ID: Guid of the record of that entity. Typically this is dynamically retrieved from other operations above this step (I’ve simply hard-coded one)
Parameters: In my example, I’m passing a parameter called ‘InputName’ and I’m passing a string called “Account Name”
- Operation-Now, once my Bound Action is executed, I can see the below results which it will return i.e. OutputName field after composing with InputName inside the Action
- Further, you can use the following Output from the Bound Action i.e. the Response or the Output parameters the Action is sending.
Unbound Action meaning calling an Action that is not bound to any entity in Dynamics 365 and is set to None (Global)
- In my Unbound Action, I am simply passing InputName through to the OutputName field as is.
- Now, I’ll use Perform an unbound action from the Actions in Common Data Service (Current Environment) connector
- Once you select this action, you simply need to select the name of the Action from Dynamics 365 itself (Again, not Display Name) and pass along any Input parameters for the same, if any.
- Operation – Now, once you execute this, the Action will execute and give you a response as below
- Further, you can select what you want to use from the response of the action step i.e. either the Response itself or the Output Parameters, if any.
Here are some other Power Automate / Flow posts that might interest you –
- Switch-Case in a Flow | Power Automate
- Enable Flow button on D365 Ribbon
- Secure Input/Output in Power Automate Run History
- Setting Retry Policy for an HTTP request in a Flow | Power Automate
- Using Parse JSON to read individual List Records in Flow|Power Automate
- Make HTTP request from Flow in Power Automate
- Retrieve only active Dynamics 365 CE licensed Users in CDS connector in Power Automate
- Create a To-Do List Item of Important Outlook Emails using Power Automate
- RSS notifications to your phone using Power Automate
- Selecting (Current) in Environment in Power Automate CDS connector and why it matters
- Button Flow in Power Automate to replicate a Quick Create Form in D365 CE
- Approval Process using Power Automate
Hope this simple example helps explain the actions!