Skip to main content

HSD’s Dynamics 365 Technical Consultant, Wasi Salman provides an announcement on some depreciations coming to Power Apps, Power Automate and Customer Engagement Apps that will help IT professionals plan their next release.

These announcements have been made over last year or two. Admins, developers and IT professionals can use following information to plan their next release. 

Internet Explorer 11 support 

Since December 2020, Microsoft Internet Explorer for Dynamics 365 and Power Automate is deprecated. With 2022 Wave 2, Internet Explorer will be completely blocked, and will be asked to switch to modern browsers.  

This will affect Microsoft Dynamics 365 users and Microsoft Power Platform products that are designed to be used through IE 11 interface. Microsoft recommends that customer transition to Microsoft Edge. 

Skype integration with Customer Engagement 

Effective July 2019, Skype integration with Customer engagement apps is depreciated and is no longer supported after July 31, 2021.  

This includes:

  • presence indication backed by Skype for Business will no longer work, and;
  • indication in hover cards, lookup fields and lookup columns in grid.

Currently there are plans to support these features via Teams. 

There is a plan to transition to Teams because of its capabilities go beyond then Skype. 

Dataverse OData v2.0 Service removal 

Microsoft plans to remove Dataverse OData v2.0 Organisation Data service on November 11, 2022. This does not involve the deprecated Organisation Service SOAP endpoint. At this time, no date has been announced for removal of SOAP endpoint. 

OData v2.0 Organisation Data service was initially announced with CRM 2011, any code that uses this service should be migrated to use the Web API before that time. 

Microsoft Dynamics 365 application for Windows 

Effective April 2021, Microsoft Dynamics 365 app for Windows that allows running Customer engagement apps (Sales, Customer Service and Marketing) has been deprecated. 

After April 1, the 2021 app is removed from Microsoft Store and is no longer supported. Microsoft recommends using a web browser for these applications. 

Dynamics 365 Connector 

From May 5, 2020, Dynamics 365 connector used for Flows, Logic Apps, and Canvas Apps if officially depreciated. Instead of using this connector, start using Microsoft Dataverse connectors where possible. Currently, you may not be able to use Microsoft Dataverse connectors in following areas: 

  • Microsoft Dataverse connector is not available in Logic Apps. 
  • Microsoft Dataverse connector do not enable cross environment connections. 
  • Microsoft Dataverse connector cannot be used for Canvas apps that use Power Apps for Windows client. 
     

In the case that you cannot use Microsoft Dataverse connector, you should be using Microsoft Dataverse (legacy). This connector has all the capabilities of Dynamics 365 connector and included some improvements. 

Dynamics 365 for Outlook 

Effective March 2020, the legacy Dynamics 365 for Outlook (also referred as Outlook COM add-in) was deprecated and is no longer available for Customer Engagement apps. Microsoft recommends using modern Dynamics 365 App for Outlook. 

Dynamics 365 Customer Engagement (on-premises) users can continue to use legacy Dynamics 365 for Outlook. However, Microsoft recommends transitioning to modern app at earliest. 

Microsoft 365 Groups and Yammer 

Effective February 2022, support for Microsoft 365 Groups (previously known as Office Groups) and Yammer in Dynamics 365 will be deprecated. This will impact customers who use Microsoft 365 Groups and/or Yammer for collaboration in Dynamics 365. We recommend that customers transition to Microsoft Teams for more advanced collaboration functionalities. 

Existing customers can create teams from their existing Microsoft 365 Groups and map them to individual records as per the requirements. They can also continue to use Microsoft 365 Groups but have a custom experience to host it inside Dynamics 365. 

Support for viewing and managing application users in legacy web client is deprecated 

Effective February 2022, the list of “Application Users” will not be available under Advanced Settings > Security > Users. You can use the Power Platform admin center to view and manage application users. 

Some Client APIs are deprecated 

Following client APIs are deprecated and will continue to be available and supported until they are officially removed from a future major release. 

deprecated Client API Replacement Client API 
Xrm.Page Forms: ExecutionContext.getFormContext 
 Commands: Send it as the PrimaryControl parameter 
Xrm.Page.context Xrm.Utility.getGlobalContext 
Xrm.Page.context.getQueryStringParameters formContext.data.attributes 
Xrm.Page.context.getTimeZoneOffsetMinutes globalContext.userSettings.getTimeZoneOffsetMinutes 
Xrm.Page.context.getUserId globalContext.userSettings.userId 
Xrm.Page.context.getUserLcid globalContext.userSettings.languageId 
Xrm.Page.context.getUserName globalContext.userSettings.userName 
Xrm.Page.context.getUserRoles globalContext.userSettings.securityRoles 
Xrm.Page.context.getIsAutoSaveEnabled globalContext.organizationSettings.isAutoSaveEnabled 
Xrm.Page.context.getOrgLcid globalContext.organizationSettings.languageId 
Xrm.Page.context.getOrgUniqueName globalContext.organizationSettings.uniqueName 
Xrm.Page.data.entity.getDataXml No change in the method, but use “typename” instead of type for lookup attributes. 
GridRow.getData GridRow.data 
GridRowData.getEntity GridRowData.entity 
Xrm.Mobile.offline Xrm.WebApi.offline 
parent.Xrm Use one of the following: 
   
 a) Use a custom control created using Power Apps component framework instead of HTML web resources. 
   
 b) On forms, use the getContentWindow method of the web resource control. 
   
 c) If the getContentWindow method doesn’t work, you can use parent.Xrm to get to the Xrm object inside an HTML web resource. If the HTML web resource is opened in a new window, then you should use opener.Xrm instead. 
addOnKeyPress Use a custom control created using Power Apps component framework 
fireOnKeyPress Use a custom control created using Power Apps component framework 
removeOnKeyPress Use a custom control created using Power Apps component framework 
showAutoComplete Use a custom control created using Power Apps component framework 
hideAutoComplete Use a custom control created using Power Apps component framework 
Xrm.Utility.alertDialog Xrm.Navigation.openAlertDialog 
Xrm.Utility.confirmDialog Xrm.Navigation.openConfirmDialog 
Xrm.Utility.getBarcodeValue Xrm.Device.getBarcodeValue 
Xrm.Utility.getCurrentPosition Xrm.Device.getCurrentPosition 
Xrm.Utility.isActivityType Xrm.Utility.getEntityMetadata 
Xrm.Utility.openEntityForm Xrm.Navigation.openForm 
Xrm.Utility.openQuickCreate Xrm.Navigation.openForm 
Xrm.Utility.openWebResource Xrm.Navigation.openWebResource 
 
globalContext.organizationSettings.baseCurrencyId globalContext.organizationSettings.baseCurrency 
globalContext.userSettings.securityRoles globalContext.userSettings.roles 
globalContext.userSettings.transactionCurrencyId globalContext.userSettings.transactionCurrency 
getData and setData for Silverlight web resources None 
formContext.data.entity.save formContext.data.save 
ClientGlobalContext.js.aspx None 
getObject getContentWindow 
  

Keeping track of these deprecations is important and will help keep you ahead of the game.

References

https://docs.microsoft.com/en-us/power-platform/important-changes-coming

Make sure you check out more of HSD’s blog posts by visiting https://www.hsd.com.au/blog/ and follow us on LinkedIn for up-to-date activity from HSD.