Breaking news from around the world
Get the Bing + MSN extension
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View 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 | Talent TechTalks | Upcoming TechTalks
On current project, we've 3 different teams who do development at Dev instance. They add their components in their own solutions. The problem is the same components get released to production instance without the knowledge of the other team(s). We would like to handle it in a proper way. Nothing needs to be released without the knowledge of that particular team.
Is there any way to manage this? Say when a particular team tries to export their unmanaged solution from the Dev instance, they would be notified that the similar components are part of the other team solution(s) and henceforth you should not move the solution to PROD instance.
Any assistance would be appreciated.
I suggest you have a read of the following document: Solution Lifecycle Management: Dynamics 365 for Customer Engagement apps
It is an excellent resource providing guidance and direction.
Business Applications communities