end-of-life for Dynamics Field Service (online) legacy versions by February, 2020

May 22nd, 2019 by Stephen Jones Leave a reply »

Last week Microsoft announced the retirement of all legacy versions (web client and mobile) of Dynamics 365 for Field Service (online) by the end of February, 2020. This change aims to provide all users access to the latest capabilities and improvements, and offer a better support experience.

All customers must update to Field Service version 8.x by February, 2020

These versions are impacted:
• Field Service web client versions 7.x and 6.x
Field Service mobile (2017) on all platforms including iOS and Android

Regular updates on these versions will continue until October, this year and Microsoft will continue to provide support until December, 2019.

This change does not impact Dynamics 365 for Field Service (on-premises) versions.

Most of the Recent improvements are only available in Field Service version 8.x onwards, so organizations using earlier versions are missing out on new capabilities such as:
• Improved scheduling experiences
• Improved IoT scenarios and enablement
• Multi-resource work orders
• Crew scheduling
• Pools
• Facilities-based scheduling
• Geo-fencing
• SLA improvements
• Entitlements
• and more…

Field Service 8.x has been available via opt-in on the insider portal (https://experience.dynamics.com/insider) since last August. There are significant changes to the user interface as part of the move to the Dynamics 365 Unified version. https://docs.microsoft.com/en-us/dynamics365/customer-engagement/admin/about-unified-interface

Consider:
• Do not install this directly on your production environment. This upgrade should initially be done in a non-production environment with change management and release controls.
We don’t anticipate any breaking changes, but i test to ensure that no customizations are impacted by the upgrade process. Run the Solution Checker to assess potentially problematic customizations.
• Field Service version 8 relies entirely on the Unified Interface. All navigation is controlled by model driven apps.
Field service version 7 had significantly different navigation which will no longer be available when using Field Service.
• Field Service mobile in version 8 takes advantage of the new Field Service Mobile app and a new mobile project.

Use of previous project templates or mobile apps, including Field Service Mobile (2017) and Field Service Mobile (2016), on Field Service version 8 is not supported.

Plan to follow Microsoft’s detailed steps to build a derivative mobile project against the new project template and then move your mobile users to the new app.

• Update internal documentation and conduct internal training to manage the organizational impact of changes from the navigation, mobile app, and any potential functionality impacts discovered by testing or the Solution Checker.

• Once ready, enable on your production environments.

Note. There is a trials version. When Field Service is not installed on an org, then you can install the Field Service Trial from App Source. However, do not attempt this on an org with Field Service version 7 because this install will fail. It is blocked by Microsoft to protect organizations from accidentally upgrading to the latest version, without an understanding of the impact of this upgrade.

Advertisement

Comments are closed.