Welcome to our blog where will be sharing tip, tricks and detailed walk-throughs covering all areas of Dynamics 365 but primarily focused on the Field Service and Project Service Apps, Scheduling and integration using Microsoft Flow and the Common Data Service (CDS). We hope you find the blog posts useful and please feel free to comment if you would like us to elaborate on any particular area. 

  • Iain Dalgleish

Seeing double - the 2 Flow CDS Connectors explained

There are 2 CDS connectors available in Flow with different features and which also require different approaches to setting certain data types on CRUD operations.


When you are in any non-default environment Flow and choose to create an action for a Flow that resides inside, or outside, a solution, you will see a Common Data Service connector in the default list.

Even if you search for "Common Data" you still only see one connector and the available triggers/actions.

The screenshot below provides a summary of the triggers and actions available.

However, if you created your Flow inside a Solution and then search for "Common Data" you will see another Common Data Service connector, Common Data Service (current environment).

Selecting on this connector gives a very different list of triggers (only 1 at the moment) and actions.

As the name implies you do not need to specify the environment as it runs in the context of the environment it is being executed from and the triggers for Create,Update and Delete have been consolidated into one allowing you to also combine Flow actions on combinations of these triggers e.g. Create and Update.


We can also see a number of new actions which I will go into in future posts, particularly Relate records and Unrelate records (which may also be called Associate and Disassociate in slightly older environments) and Perform a bound action and Perform an unbound action. There is also a Predict action which allows you to leverage a Prediction Model you have built with AI Builder to predict a result based on the data passed in.


Not only is there more functionality inside this connector but the way you interact with it is slightly different from the older connector and I will be covering some of these in upcoming posts, including how you set and clear lookup values in the new connector.


You might also notice that the "When a record is selected" trigger is not available in the new connector and this makes sense given how this is currently implemented which I will also cover in subsequent posts.


162 views0 comments