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 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
With the deprecation announcement of the Dynamics 365 connector, a common question is guidelines for interacting with Dynamics 365 Apps using Common Data Service Connectors. Why I say connectors is because there are two Common Data Service connectors. This post on our PFE team blog describes how to find these different connectors and differences in triggers and actions.
At high level, the Common Data Service (Current Environment) connector should be the first choice, and if that doesn’t serve the requirement then use the Common Data Service connector as next option.
So why should the Current Environment connection be the first choice compared to other one? Here I talk about a series of advantages of the "Current Environment" connector:
Writing Filter or Expand Query formulas can be eased out using the FetchXML Builder plugin of the XrmToolBox community tool. The View drop down has the option to generate Power Automate parameters based on current FetchXML you create:
The "When a record is selected trigger" trigger is not available with Current Environment connector, it's available with Common Data Service connector. This is the only trigger requirement one can think of using Common Data Service connector.
The Ideas page on Power Automate Community website is a good tool to find and vote on existing ideas or submit your own suggestions/ideas.
Hope this helps!
Business Applications communities