Common Data Service (Current Environment) Cheat Sheet

• Trigger Condition:
  <Select the operation>
• Entity:
  <Select the Entity>
• Scope:
  <Select the scope>
  (More info about SCOPE)
• Filtering attributes: Use the field
  “Name” not “Display
  name”.
• Filter expression:
  Ex: statuscode eq 1
• Postpone until: Ex: estimatedclosedate
  (The trigger will wait until the date is reached)
• Run as:
  <Select the User>

Other references:

• Build Efficient Flows Using Filter Expression in CDS (current
  environment) Trigger
  – by Linn Zaw Win
• Every Power Automate (MS Flow) Filter Query You Ever Wanted To
  Know
  – by Prashant Shukla

• Add an input:
  <Select the type of user input>

Calling the Power Automate

• Open a Business Process Flow and Add a “Flow Step”

Other references:

• BPF Flow Step as a Trigger in CDS (Current Environment) connector
  | Power Automate
  – by Priyesh Wagh

• Entity name:
  <Select the Entity>
• Values based on field types:
• Text field:
  <Text value> 
• Number or Currency:
  <Value>
• Option set:
  <Select the value>
• Lookup:
  Ex: contacts(<RecordGUID>)
• Datetime:
  Ex: 2020-04-10T10:30Z If
  your datetime has a “Z” at the end, it means it’s in UTC.
• Multi Select Option Set:
  Ex: 2, 3, 4

Other references:

• How to Set Lookup Field Value in Common Data Service (current
  environment) Flow Connector
  – by Linn Zaw Win 

• Entity name:
  <Select the Entity>
• Item ID:
  <RecordGUID>

• Entity name:
  <Select the Entity>
• Item ID:
  <RecordGUID>
• Select Query:
  Ex: emailsddress1, firstname
• Expand Query: Using the Fetch XML Builder

Other references:

• FetchXML Builder
  – by Jonas Rapp

• Entity name:
  <Select the Entity>
• Item ID:
  <RecordGUID>
• Field name: <Select the Entity image field>

• Entity name:
  <Select the Entity>
• Select Query: Use the field
  “Name” not “Display
  name”
• Filter Query:
  Ex: companyname ne null
• Order by: Use the field
  “Name” not “Display name”.
• Expand Query: Using the Fetch XML Builder
• Fetch XML Query: Use “Advanced Find” in Model Driven Apps or
  D365 and “Download fetch XML”.
• 
• Top Count: Use the field
  “Name” not “Display name”.
• Skip token: TBC (I couldn’t find any good example to make
  this work. Please contact me if you know how / why to use it).

Other references:

• List Records – Use Expand Query to Retrieve Related Data in
  flow
  – by Linn Zaw Win
• Every Power Automate (MS Flow) Filter Query You Ever Wanted To
  Know
  – by Prashant Shukla
• FetchXML Builder – by
  Jonas Rapp

• Entity name:
  <Select the Entity>
• Action name:
  <Select from the available Entity Actions>
  (Web API Action Reference)
• Item ID: <RecordGUID>
• Other parameters: Depends on the Action you have
  selected 

• Action Name:
  <Select an Action>
  (Web API Action Reference)
• Other parameters: Depends on the Action you have selected

• Model:
  <Select a Model> (AI Builder in Power Automate overview)
• Other parameters: Depends on the Model you have selected

• Entity name:
  <Select the Entity>
  (Parent Entity for 1 to n relationship)
• Item ID:
  <RecordGUID>
• Relationship:
  <Select the Relationship>
• URL:
  Ex:
  https://[yourenvironment].crm.dynamics.com/api/data/v9.1/leads(GUID)

• Entity name:
  <Select the Entity>
• Item ID:
  <RecordGUID>

• Entity name:
  <Select the Entity>
• Item ID:
  <RecordGUID>
• Field name:
  <Select the Entity image field>
• Content:
  <binary file>

“Executes a changeset request” is a set of CDS change
(Create/Update/Delete) actions in which failure of one of the steps will
cause the transaction to rollback for previous actions within “Executes
a changeset request” step.

More info on: 

• New Action “Executes a changeset request” in Microsoft Flow
  Common Data Service (current environment) connector
  – by Linn Zaw Win