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 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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
Doing some upgrade testing from 2013 to 2015 and I've found that in the Case/Incident entity, CRM has modified several "Case Type" fields. For example, I have an existing Case Type called Bug with a value of 2, that after upgrading to 2015 CRM renames it to Problem (still has the value of 2 so I know it is the same one), but then automatically creates a new Bug with a value of (266,900,000). Change Request (value of 3) changes to Request, but doesn't recreate the original Change Request like what happened with Bug. Question/Training turns into just Question (same value of 1).
Just a little wary of the upgrade at this point if it is automatically renaming items in fields. Still looking for other things it may have changed. Any idea what would have caused this?
Option set labels will always be overwritten upon import of managed solution. Have you imported any other managed solution? You can rename again and move on or Keep OOTB label values, and create new values in the option set to support additional requirements. Best Practice is try to avoid changing label name out-of-the-box values.
Here's the thing though, I just setup a brand new organization in 2015 as a test and there are three fields listed in Case Type: Question, Problem, Request. I did the same for 2013 (brand new organization) and found the same results. We recently upgraded from 2011 to 2013 and CRM didn't reset or replace any of these fields like this so I'm trying to figure out why 2015 would.
The answer to why will be in your upgrade path from 2013 to 2015: Between CRM2013 and CRM2015 there is service pack namely: Microsoft Dynamics CRM 2013 Service Pack 1 ( Microsoft Dynamics CRM Online Spring ’14) , This CRM 2013 SP 1 upgrade has changed the solution components. This is an enhancement to service module and this does not need to be added to newly Provisioned CRM 2015 instances. Fresh CRM 2013 instance also does not have the feature of CRM 2013SP1.
Hope this helps.
I was typing a whole response out about how our current live CRM system is 2013 SP1 (update 3) and we don't see it.....BUT I just realized after applying SP1 I never did the "install system updates" in the Settings area that applies many of the SP1 changes. Things are finally starting to make sense because yes like you said, 2015 forcefully applies those changes.
Gashaw, one final question. Do you know of a place that lists a complete list of changes with SP1? I've seen site after site that lists 5-10 bullet points with the general changes, but nothing that specifically mentions the solution components changing. Just trying to make sure other small changes don't slip by.
AT high level list includes:
Form and View Changes
• User form got additional sub-grid
• Case Entity has new Updated form “Case”
• Additional and modified views on Case entity
Sitemap/Form navigation change:
• New Sub area under Setting >Service management
• Social Profile which appears as a sub-area within the Service area
• Contact and account added mew navigation “Entitlement” and “Social Profile”
• New and modified System Dashboards
• Entitlement Template
• Entitlement Channel
• Routing Rule
• Routing Rule Item
• SLA Item
for above entities (blank for custom security roles)
Business Applications communities