Deprecated(Removed) and Replacement JavaScript statements in Dynamics 365 Version 9.x

Summary : Dynamics 365 Version 9.x JavaScript Client API

Deprecated/Removed and Replacement JavaScript statements in Dynamics 365 Version 9.x JavaScript

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.userSetings.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
addOnKeyPress	Use a custom control
removeOnKeyPress	Use a custom control
showAutoComplete	Use a custom control and corresponding UI
hideAutoComplete	Use a custom control and corresponding UI
Xrm.Utility.alertDialog	Xrm.Navigation.openAlertDialog
Xrm.Utility.confirmDialog	Xrm.Navigation.openConfirmDialog
Xrm.Utility.isActivityType	Xrm.Utility.getEntityMetadata
Xrm.Utility.openEntityForm	Xrm.Navigation.openForm
Xrm.Utility.openQuickCreate	Xrm.Navigation.openForm
Xrm.Utility.openWebResource	Xrm.Navigation.openWebResource

Dynamics 365 Version 9.x JavaScript Client API

Dynamics 365 Version 9.x JavaScript Client API

      

    The Client API object model for Dynamics 365 provides to us objects and methods that can used to apply custom business logic with JavaScript.

It’s important that we need to understand the Client API object model to effectively write and use your JavaScript code in D365.

Object	Description
executionContext	Execution context for an event in CRM forms and grids.
formContext	Provides a reference to a form or an item on the form against which the current code executes. To get the formContext object, use the executionContext.getFormContextmethod.
gridContext	Provides a reference to a grid or a sub grid on a form against which the current code executes.
Xrm	Provides a global object for performing operations that do not directly impact the data and UI in forms, grids, sub grids, controls, or attributes. For example, navigate forms, create and manage records using Web API.

How to develop a daily/schedule Jobs for Dynamics 365

Subject: How to develop a daily/schedule Jobs for Dynamics 365

v  We have a couple ways to develop the scheduler jobs. The following approaches are most commonly used.

    

        1. Console Application (C#) and Scheduling.

        2. Scribe packages and Scheduling.

        2. SSIS Packages and Scheduling.

v One of the major parameter for deciding the approach is volume of the data needs to be updated/created.

              If you need to perform operation for less than 10k then we will be able to manage with Console App.

              If volume of the data is greater than 10k then we need to go with SSIS or Scribe jobs.

Step by step process to develop the Console Application for Dynamics 365.          

             

Common Scenarios :

1.Sending the mails to remainder mails from CRM for Approval or pending action for any entity.

2.Retrieving data from other data source and Create/Updating in Dynamics 365.

3.Perform the some calculations and updating the CRM.

Coding:

I will develop a simple console application here and show the step by step.

Dynamics 365 CRM Portals - Supported Features in Customer Self- Serve portal, Partner Portal,Employee Self- Service Portal,Community Portal and Custom Portal

Subject: Dynamics 365 CRM Portals - Supported Features between the Portals

Most of the people getting confused when configuring the CRM Portals. which type of the portal should take.

In D365 Portals, we have 5 types of websites.

1. Customer Self- Serve portal
2. Partner Portal
3.Employee Self- Service Portal
4. Community Portal
5. Custom Portal

Here I listed the Features difference among these five websites

Features	Customer Self-Service Portal	Partner Portal	Employee Self-Service Portal	Community Portal	Custom Portal
World Ready	Yes	Yes	Yes	Yes	Yes
Multi-Language Support	Yes	Yes	Yes	Yes	Yes
Portal Administration	Yes	Yes	Yes	Yes	Yes
Customization and Extensibility	Yes	Yes	Yes	Yes	Yes
Theming	Yes	Yes	Yes	Yes	Yes
Content Management	Yes		Yes	Yes
Knowledge Management	Yes	Yes	Yes	Yes
Support/Case Management	Yes		Yes	Yes
Forums	Yes		Yes	Yes
Faceted Search	Yes		Yes
Profile Management	Yes		Yes
Subscribe to Forum Thread	Yes		Yes
Comments	Yes		Yes	Yes
Azure AD Authentication			Yes
Ideas				Yes
Blogs				Yes
Project Service Automation Integration		Yes
Field Service Integration		Yes
Partner On boarding		Yes
Portal Base	Yes	Yes	Yes	Yes	Yes
Portal Workflows	Yes	Yes	Yes	Yes	Yes
Web Notifications	Yes	Yes	Yes	Yes	Yes
Microsoft Identity	Yes	Yes	Yes	Yes	Yes
Identity Workflows	Yes	Yes	Yes	Yes	Yes
Web Forms	Yes	Yes	Yes	Yes	Yes
Feedback	Yes	Yes	Yes	Yes	Yes