Microsoft Dynamics 365June 12, 2017
Dynamics 365 is a product line of enterprise resource planning (ERP) and customer relationship management (CRM) applications announced by Microsoft in July 2016 and on general release November 1, 2016. Dynamics 365 is sold in two editions, the Business Edition for small and medium businesses (SMBs), and the Enterprise Edition for medium to large organizations. The Business Edition includes the Financials application.
The Enterprise Edition comprises Dynamics CRM applications (field service, sales, project service automation, and customer service) plus Microsoft PowerApps, together with Microsoft's premier ERP product, known as Dynamics 365 for Operations.
From July 1, 2017, the Dynamics 365 line was repackaged. The CRM applications are now called the Customer Engagement Plan. The ERP application is now called Dynamics 365 for Finance and Operations, however it is only available as part of the Unified Operations Plan which also includes the standalone applications Dynamics 365 for Talent and Dynamics 365 for Retail. Together, the two plans form the Dynamics 365 Plan.
Use digital intelligence to reimagine what’s possible for your business. Dynamics 365 unifies CRM and ERP capabilities into applications that work seamlessly together across sales, customer service, field service, operations, financials, marketing, and project service automation. Start with what you need, add applications as your business grows. Rethink what’s possible for your business when you:
- Better engage customers
- Empower employees
- Optimize operations
- Reinvent products and business models
Transform your business processes and better engage customers using intelligent applications that work seamlessly together in the cloud.
Customer Insights is a Azure-based SaaS service that enables organizations of all sizes to bring together data from multiple sources, including Microsoft Dynamics 365, and generate knowledge and insights to build a holistic 360° view of their customers. The Customer Insights Programming Referencedocuments the two sets of REST interfaces provided by this service: the Azure Resource Manager (ARM) APIs and the Hub APIs. These interfaces enable developers to extend custom applications, as well as to automate Customer Insights Hub administrative operations.
2.Introducing editable grids:
The new editable grids feature provides inline editing capabilities in the main grid and subgrids without having to switch records or views. The new editable grids are supported in the web client, Dynamics 365 for phones and Dynamics 365 for tablets.The editable grids also support client-side events and methods that can be used to write custom client extensions according to your business need.More information: Use editable grids and Editable grid objects and methods (client-side reference).
3.Data Export service:
The ability to replicate Dynamics 365 data to an external SQL database provides a lot of flexibility for generating reports. Data Export is an add-on service made available as a Microsoft Dynamics 365 (online) solution that adds the ability to replicate Dynamics 365 (online) data to a Microsoft Azure SQL Database store in a customer-owned Microsoft Azure subscription. The supported target destinations are Microsoft Azure SQL Database and Microsoft Azure SQL Server on Microsoft Azure virtual machines. Data Export intelligently synchronizes the entire Dynamics 365 schema and data initially and thereafter synchronizes on a continuous basis as changes occur (delta changes) in the Microsoft Dynamics 365 (online) system.
The Data Export service provides an interface for managing configuration and ongoing administration of this service from within Dynamics 365 (online). Developers can write code to interact with this service.
4.Web API Enhancements:
a) Access to local data while Dynamics 365 for Outlook is offline:
When you write form scripts that use the Web API, these scripts can work using the local data in Dynamics 365 for Outlook when the user is offline. This capability has been available for the Organization service (SOAP endpoint) and the Organization Data service (OData v2), but was not previously available with the Web API.
b) Return entity data on create or update:
Sometimes you want to retrieve an entity right after you create or update it. Before this release, you needed to use two operations. The POST request to create an entity returns an HTTP 204 (No content) status and a Uri to the entity created is returned in the OData-EntityId header property. You can then use this Uri with a GET request to retrieve the created entity. This is because the default preference is to apply the return=minimal preference.A PATCH request applied to update an entity will simply return HTTP 204 (No content) status when successful.
With this release you can specify the return=representation preference in the header of the request. A successful POST request will return HTTP 201 (Created) and include the entity properties you select. You can select which properties are returned by using the $select system query option.A successful PATCH request will return HTTP 200 (OK) with the full entity.
c) Reference metadata by name:
With this release, you can use the name of certain metadata properties as alternate keys to reference an item of metadata. This will make it easier to query metadata using the Web API. Before this, you needed to perform a query to access the MetadataId of a particular item of metadata before you could retrieve it using that MetadataId as the key.
5.Activity Sorting Control:
There is a new sortdate attribute on the activitypointer entity that you can use to control how activities are sorted by date. For example, if you want to have email entities sorted by the senton attribute value rather than the modifiedon attribute value, create a plugin or workflow to set the sortdate value equal to the senton value only for email entities. Otherwise, set the sortdate attribute equal to the modifiedon value. Then use this sortdate attribute in the orderby criteria for your query.
6.Programmatic management of Product Properties:
You can now programmatically create and manage product properties in Dynamics 365, which enables you to completely automate the product catalog in Dynamics 365 and integrate it with third-party software. Earlier, you could programmatically create and manage product family, product or bundle, but not the product properties.
7.Define access permission for modular business apps programmatically:
The new modular business apps are based on the concept of functional separation that let you choose to expose a limited set of functionality for users in Dynamics 365 depending on their area of work. Developers can programmatically retrieve and associate or dissociate a modular app with security roles in Dynamics 365 to define the app’s access permission.
8.Use form scripts to add icons with tooltip text for view columns:
Use form scripting in Dynamics 365 to add icons with tooltip text that is based on the column value in the view. You can also specify localized tooltip text.
9.Introducing client APIs for creating and managing records in Dynamics 365 mobile clients while working offline:
Use the new client APIs under the Xrm.Mobile.offline namespace to create, retrieve, update and delete records in Dynamics 365 for phones and Dynamics 365 for tablets while working in the offline mode. These new client APIs will work only if you are in the offline mode and for entities that are enabled for mobile offline synchronization.
10.Enhanced client API support in the interactive service hub.
Use server-to-server (S2S) authentication to securely and seamlessly communicate with Microsoft Dynamics 365 (online & on-premises) with your web applications and services. S2S authentication is the common way that apps registered on Microsoft AppSource use to access the Dynamics 365 data of their subscribers. Both single-tenant and multi-tenant applications can use this feature.S2S authentication means you don’t need to use a paid Dynamics 365 user license when you connect to Dynamics 365 tenants. There is no license fee for the special application user account you will use with S2S authentication.
With S2S authentication a special Dynamics 365 unlicensed application user account is created and includes information about your application registered with Azure Active Directory (Azure AD). Rather than user credentials, the application is authenticated based on an application user identified by an Azure AD Object ID value which is stored in the Dynamics 365 user record. The Dynamics 365 application user is associated with a security role which controls the kinds of data and operations the application is allowed to perform.
1) Execute SDK messages and actions from processes:
It is now possible to execute select SDK messages and custom actions from workflows, process dialogs, and other actions.
2) Access business process instances using the Web API:
Business process flow instances are fully exposed through the Dynamics 365 Web API, allowing developers and system integrators to manipulate processes programmatically from an external custom application. The Web API allows you to apply new processes to entity records, switch the process status from Active to Finished or Aborted, and switch the stage of the process flow.
3) Associate multiple business processes with a single entity record:
More than one business process can be associated with a single entity record. You can switch between the processes by using the extended SetProcess action or message. Switch between business processes without losing the state and progress of each process.
Business processes now support security roles as a means of restricting user access to the process.
4) Client API enhancements for business processes:
The setActiveProcess method is updated and some new client APIs are added under the Xrm.Page.data.process namespace to handle the new functionality for concurrent business flows and the ability to mark a process as Active, Finished or Abandoned.
5) Client API enhancements for adding notifications with actions:
Earlier, you could set only an error type of notification for a control in Dynamics 365 using the setNotification client API. Now, you can add two types of notification for a control using the new addNotificationmethod: error or recommendation.
13.New Messages Introduced
14.New Entities Introduced
15.New Privileges Introduced
16.App Modules Introduced
With this release, a new concept has been introduced to Dynamics 365 for Sales (formerly Dynamics CRM). This concept is the ability to have multiple Apps within the product. First off, note that this feature is in preview only mode for this release.
17.Sitemap Designer Introduced for Apps
he Site Map Designer is a visual way to update your sitemap for your app. The Site Map Designer allows you to update the default site map (which was the site map we’ve known and loved over the years for past versions of CRM), as well as app specific site maps.
18.Power BI In-Built
The Power BI for Office 365 cloud service works with Microsoft Dynamics 365 to provide a self-service analytics solution. Power BI automatically refreshes the Microsoft Dynamics 365 (online) data displayed. With Power BI Desktop or Microsoft Office Excel Power Query for authoring reports and Power BI for sharing dashboards and refreshing data from Microsoft Dynamics 365 (online), sales, marketing, and service personnel in your organization have a powerful new way to work with Dynamics 365 data.
19.Dynamics 365 App for Outlook
Use Microsoft Dynamics 365 App for Outlook to tap the power of Dynamics 365 while you’re using Outlook on the desktop, web, or phone. When Dynamics 365 App for Outlook is installed, depending on which version of the app you have installed, you’ll see a Dynamics 365 pane or window next to a selected Outlook email message, or when you’re composing an email message or setting up a meeting or appointment.