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
Hi,I have a customization of one of the standard c# projects (EPApplicationProxies), after of the latest CU update (6.3.6000.8144) a conflict search utility found that this project has been changed. I am unable to merge conflicts using compare tool (ISV and SYP layer) and "Merge code automatically" option doesnt recommend to use in this case because its will change all my customization layer.Do you know how can I handle this issue?Regards, Roman
Do you have a lot of changes in EPApplicationProxies? Probably the easiest solution would be to remove customizations and apply them again manually.
One of the problems is that I don't know exactly how many changes was in that project, and I probably won't be able to reproduce all the changes exactly again
You still could try to compare projects with customizations and without customizations with external tools, but if you don't have the knowledge and any kind of documentation of what was done before it could be quite difficult.
Also I resolved problem by adding missing elements through VS
Business Applications communities