One of the limitations in using Common Data Service (current environment) connecter in Power Automate comparing to the classic workflow WAS the inability to get the display name of the lookup value or the label of the option set value in one simple query. However, this is actually not the limitation of the platform itself. It seems that the CDS (current environment) actions did not use…
Continue Reading noreply@blogger.com (Linn Zaw Win)’s Article on their blog
Get the Lookup Display Name and Option Set Value Label in a Single Query Using a CDS (Current Environment) Connector FormattedValue Property
One of the limitations in using Common Data Service (current environment) connecter in Power Automate comparing to the classic workflow WAS the inability to get the display name of the lookup value or the label of the option set value in one simple query. However, this is actually not the limitation of the platform itself.
Blog Syndicated with noreply@blogger.com (Linn Zaw Win)’s Permission
More About This Author
Array
#Dyn365CE2021.01.17Retrieve more than 100,000 Dataverse Rows with List Records Action in Cloud Flow Using Skip Token
#Dyn365CE2021.01.08Populate Activity Party Value with JSON Array in Power Automate
#Dyn365CE2020.12.15Perform Bound/Unbound Action with EntityType Parameters in Power Automate
#Dyn365CE2020.12.05Dynamically Populate Polymorphic Lookup Value in Power Automate without using Condition Step
