Dynamix Academy

The Perfect Experience to learn Microsoft Dynamics 365

Dynamics 365 v9 Deprecated Client API

In this article, we will see yet another change in Dynamics 365 v9 Deprecated Client API.

  • Some of the existing client APIs are deprecated to reorganize the Xrm client API object model to better align with the need of using the same client scripts without having to change them based on the context or the client (web client or the new Unified Interface) where they run.
  • You should plan to use the new client APIs mentioned in the Replacement Client API column instead of the deprecated ones

Dynamics 365 v9 Client APIs are deprecated

You should plan to use the new client APIs mentioned in the Replacement Client API column instead of the deprecated ones.

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

Find Full list of Dynamics 365 v9 Deprecated Client API here: https://docs.microsoft.com/en-us/power-platform/important-changes-coming#some-client-apis-are-deprecated

Deprecated Client APIReplacement Client API
Xrm.Page Forms: ExecutionContext.getFormContext
Commands: Send it as the PrimaryControl parameter
Xrm.Page.contextXrm.Utility.getGlobalContext
Xrm.Page.context.getQueryStringParametersformContext.data.attributes
Xrm.Page.context.getTimeZoneOffsetMinutesglobalContext.userSettings.getTimeZoneOffsetMinutes
Xrm.Page.context.getUserIdglobalContext.userSettings.userId
Xrm.Page.context.getUserLcidglobalContext.userSetings.languageId
Xrm.Page.context.getUserNameglobalContext.userSettings.userName
Xrm.Page.context.getUserRolesglobalContext.userSettings.securityRoles
Xrm.Page.context.getIsAutoSaveEnabledglobalContext.organizationSettings.isAutoSaveEnabled
Xrm.Page.context.getOrgLcidglobalContext.organizationSettings.languageId
Xrm.Page.context.getOrgUniqueNameglobalContext.organizationSettings.uniqueName
Xrm.Page.data.entity.getDataXmlNo change in the method, but use “typename” instead of type for lookup attributes.
GridRow.getDataGridRow.data
GridRowData.getEntityGridRowData.entity
Xrm.Mobile.offlineXrm.WebApi.offline
parent.XrmUse 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.
addOnKeyPressUse a custom control created using Power Apps component framework
fireOnKeyPressUse a custom control created using Power Apps component framework
removeOnKeyPressUse a custom control created using Power Apps component framework
showAutoCompleteUse a custom control created using Power Apps component framework
hideAutoCompleteUse a custom control created using Power Apps component framework
Xrm.Utility.alertDialogXrm.Navigation.openAlertDialog
Xrm.Utility.confirmDialogXrm.Navigation.openConfirmDialog
Xrm.Utility.getBarcodeValueXrm.Device.getBarcodeValue
Xrm.Utility.getCurrentPositionXrm.Device.getCurrentPosition
Xrm.Utility.isActivityTypeXrm.Utility.getEntityMetadata
Xrm.Utility.openEntityFormXrm.Navigation.openForm
Xrm.Utility.openQuickCreateXrm.Navigation.openForm
Xrm.Utility.openWebResourceXrm.Navigation.openWebResource
globalContext.organizationSettings.baseCurrencyIdglobalContext.organizationSettings.baseCurrency
globalContext.userSettings.securityRolesglobalContext.userSettings.Roles
globalContext.userSettings.transactionCurrencyIdglobalContext.userSettings.transactionCurrency
getData and setData for Silverlight web resourcesNone
formContext.data.entity.saveformContext.data.save
ClientGlobalContext.js.aspxNone
getObjectgetContentWindow

Also find More on Dynamix Academy :

Also find Dynamix Academy on:

Related Posts