Personalized Community is here!
Quickly customize your community to find the content you seek.
‘Better Together’ Integration forum available
We're launching a how-to forum where you can learn and engage about how Dynamics 365 integrates with other Power Platform products.
Read about Better Together forum
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
You know that annoying error you get when trying to populate a lookup field in Power Automate with the Current Environment connector? And you might have found blog posts that the solution is to set the EntitySetName before the dynamic data? Good so far – but how the hell do you find the EntitySetName? Let me help you out.
If you try to populate a CDS lookup with a dynamic value when using the CDS Current Environment Connector like this:
You will get the unpleasant error message like this:
Annoying as f… since it worked perfectly well to do exactly this with the old connector.
The solution to this unpleasant problem is to add the EntitySetName of the lookup you’re trying to populate (yes that is including prefix) and the dynamic data within parentheses.
So USUALLY you can find the out of the box entities EntitySetName here and they are usually the schemaname in plural. And USUALLY you can use the same pattern with your custom entities too – unless sometimes when your custom entity ends with an S the EntitySetName becomes something that Gollum would say from the Lord of the Ring movies. For example an entity called “sara_News” would be “sara_newses”. And don’t get me started on my tomatoes entity…
And now you’re like – I don’t care about your bad jokes where the hell did you get that screenshot from?! Well.
Get XrmToolBox if you haven’t yet, connect to your lovely organisation and get the Metadata Browser tool (special thanks to the awesome Tanguy who created it).
Search for your entity name, your prefix or what ever and scroooooll til the E’s and you’ll find EntitySetName.
Tadaa. No more guessing, trial and error running the flow, breaking vases and coffee cups in the process.
How many times can you write the word EntitySetName in one blog post? Many. Ciao.
Business Applications communities