Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
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 2 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
I have been playing with logic apps in Azure to see if I could solve a business problem in a more robust, quicker and reliable manner than the usual integration options.
When using the the Dynamics 'List Records' function, you have the option to add a filter to the query to allow you to be specific on the exact record(s) you want returned. What wasn't obvious was how to apply a filter based on a lookup field on an entity.
The current Dynamics 365 documentation's doesnt provide an example or guideline on this but after looking under the hood & analysis, the correct way to reference a lookup field in a filter is in the format "_schemaname_value" e.g the standard "primarycontactid" field on the account entity would be referenced as "_primarycontactid_value" . The query would then look along these lines
You could now for example find opportunities related to a specific account, iterate over each of those records and use that information in other areas within your logic app. Hope that saved you some time!
Business Applications communities