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
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
wasn't able to find anything so far regarding this, so I thought I'd ask if someone had a better idea than "ask MS Support".
Situation:We're using Customer Service (in the Cloud) and we've built our incident management in there. Right now, we are using a mix of new and old records to measure our KPIs:
Entitlements are configured per customer, e.g. "Customer Y - 24/7*4h", using 11 different SLA configurationsSLAs use the "Enhanced SLA" that's about to be deprecated in October. I've just run the Migration Tool (Migrate automatic record creation rules and service-level agreements | Microsoft Docs) for those, expecting the entire thing to be migrated and replaced - however all it does is create new SLA records with the new tech used - but all our entitlements are still using the old SLAs.
Is there a way to also migrate those to the new SLA records? Mass Editing seems to be disabled for this entity for some reason (Thanks, MS).
The SLA migration tool is designed to migrate legacy SLA records to UCI. If for example a legacy SLA is used within an entitlement, upon migrating the legacy SLA to UCI the SLA field within entitlement will not be updated with the new record. This can be achieved via a workflow or SDK (replace old SLA values with the new migrated ones)
Hope the above information was useful.
Business Applications communities