Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 | Talent TechTalks | Upcoming TechTalks
So you decide to “refresh” your development environment with a copy of your production environment, but too late you discover that copying an environment over another one makes canvas apps and flows created in that environment go away.
What should you do?
Other than kicking yourself for not remembering to back up your app and flow definition, don’t do anything.
When you refresh a D365/CDS environment with a copy of another environment, the flows and canvas apps that were in the environment go away, but within a short period of time you will see a restored copy of the app and flows appear in your environment. The canvas apps will be appended with the word “restored” and the date. Flows that are restored will be turned off.
You will need to share the app again with whichever users should have access to it again.
Business Applications communities