filmov
tv
Microsoft Dynamics 365 v9 Deprecated Feature Client API | xrm.page vs formcontext

Показать описание
Below are two courses that you can take to start your journey of becoming a Microsoft Dynamics 365 Developer.
The following 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. The deprecated client APIs will continue to be available and supported until they are officially removed from a future major release. A public announcement here in the documentation, on the Dynamics 365 blog, and in many other places will be made at least six months before removal.
If you are currently responsible for a Microsoft Dynamics CRM system or planning / delivering a Dynamics 365 solution, then you need to be aware of this important Microsoft announcement about the deprecation of some features and functionalities.
Xrm.Page
parent.Xrm
addOnKeyPress
removeOnKeyPress
showAutoComplete
hideAutoComplete
Microsoft defines “Deprecated” as an intention to remove the feature or capability from a future major release of Dynamics 365. The feature or capability will continue to work and is fully supported until it is officially removed. This deprecation notification can span a few years. After removal, the feature or capability will no longer work.
Hence, you should start planning replacing these features from your current Dynamics systems or avoid using these capabilities in your current Dynamics 365 implementation projects.
#dynamixacademy365 #dynamics365 #microsoftdynamics
You can also watch our Videos on playlist:
Below are two courses that you can take to start your journey of becoming a Microsoft Dynamics 365 Developer.
Let’s connect:
The following 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. The deprecated client APIs will continue to be available and supported until they are officially removed from a future major release. A public announcement here in the documentation, on the Dynamics 365 blog, and in many other places will be made at least six months before removal.
If you are currently responsible for a Microsoft Dynamics CRM system or planning / delivering a Dynamics 365 solution, then you need to be aware of this important Microsoft announcement about the deprecation of some features and functionalities.
Xrm.Page
parent.Xrm
addOnKeyPress
removeOnKeyPress
showAutoComplete
hideAutoComplete
Microsoft defines “Deprecated” as an intention to remove the feature or capability from a future major release of Dynamics 365. The feature or capability will continue to work and is fully supported until it is officially removed. This deprecation notification can span a few years. After removal, the feature or capability will no longer work.
Hence, you should start planning replacing these features from your current Dynamics systems or avoid using these capabilities in your current Dynamics 365 implementation projects.
#dynamixacademy365 #dynamics365 #microsoftdynamics
You can also watch our Videos on playlist:
Below are two courses that you can take to start your journey of becoming a Microsoft Dynamics 365 Developer.
Let’s connect:
Комментарии