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
Update: New concept called "Connection References" is in public preview and is particularly useful when moving flows across environments, updating flow definitions, automating deployment pipelines for secure, and healthy Application Lifecycle Management. Read this introduction blog post and how to use blog post to learn more.
Solution-awareness for Flow was introduced about a year ago. You might have explored or noticed Solutions in the left navigation in Power Automate designer. Since initial release, solution-awareness for the Flow has been enhanced to improve Application Lifecycle Management of Flows using CDS.
This ALM improvement partially addresses a concern I heard from a customer using Flow. The concern: “Each Flow needs wiring-up connections for trigger(s) and action(s) while importing in target environment”. I can relate with developers coming from CDS world, “hey, legacy workflows get activated during Solution import, why this need for re-wiring”.
Answer is in two parts in my opinion:
When you build the Flow, use the new Common Data Service (current environment) connector for all your actions and triggers. Common Data Service (current environment) connector is different than using Common Data Service connector and choosing (Current) from Environment drop down. Refer the screenshots:
To differentiate easily, the actions and triggers for this Common Data Service (current environment) doesn’t have the drop down to choose Environment, here is a screenshot:
You have to start from within a Solution in order to use the Common Data Service (current environment) connector as this connector is available only within a Solution.
A Flow that use connectors other than the Common Data Service (current environment) require re-wiring connection(s) and activation, which is an intentional measure to avoid unintended integrations with external systems.
Hope this helps!
Business Applications communities