Following are the New features
- Web API introduced
- Organization data service (OData v2 REST endpoint) deprecated
- CORS Support added
- Form script support for keypress events and auto-completion feature
- CRM for phones and tablets enhancements
- Knowledge management edit and search enhancements
- Solution enhancements
- Service level agreement enhancements
- Upload and manage document templates
- XRM Tooling controls now support OAuth authentication and connection strings
- New entities in CRM 2016
- New messages in CRM 2016
- New privileges in CRM 2016
New features that were added to
Microsoft Dynamics CRM Online 2015 Update 1 are now available for on-premises
organizations. One exception is the integration with Parature which is only
available for CRM Online. For a summary of new features included in that
release, see What’s
new for Microsoft Dynamics CRM Online 2015 Update 1
Web API introduced
The Web API makes it easier to
create applications across a wide variety of platforms, devices, and
programming languages.
You can perform all operations using
HTTP requests with the Web API located at [organization uri]/api/data/v8.0/.
The Web API implements OData version 4.0, an open
standard for data access. For the list of third-party libraries that support
OData, version 4.0, see http://www.odata.org/libraries/.
Use the Web API for integrations and
modern applications. For code that will run in the context of a plug-in, you’ll
continue to use the classes defined in the SDK assemblies to use the
organization service. More information:Use the Microsoft
Dynamics CRM Web API
Use Web API Within the CRM web
application using JavaScript and HTML web resources without any code to
authenticate, just as we do today with the organization (SOAP) or organization
data service (Odata v2 REST) endpoints.
Online /Internet-facing deployment
(IFD) web services authentication(from your own applications)-You must first
register the app with the Active Directory for your organization. Then you can
use the Azure
Active Directory Authentication Library (ADAL) to manage OAuth 2.0 authentication with the CRM web
service identity provider.
On-premises CRM deployment webservices
authentication(from your own applications), you’d use your Windows network
credentials to authenticate with the web services.
More information:Walkthrough:
Register a CRM app with Active Directory
A Discovery service to the Web API
has been added to maintain a parity with the SOAP endpoint.
This service enables you to
determine, at run-time, the organizations that the signed-in user belongs to.
You can retrieve information about those organizations like the organization
service URL, the CRM release version, and more.
A new feature of the Web API
Discovery service is the ability to filter the returned list of organizations
by using OData filter parameters. The Discovery service is supported by all CRM
deployment types. More information:Discover the URL
for your organization using the Web API
The new Web API provides better
capabilities over the organization data service introduced with Microsoft
Dynamics CRM 2011. It is recommend that any new code for this version should use
the Web API instead of the organization data service, hence the OData endpoint
has been deprecated, but it will remain in the application for the foreseeable
future to support backward capability. For information about using this
deprecated endpoint, see the Microsoft Dynamics CRM 2015 SDK: Use the
OData endpoint with web resources.CORS support added
The Web API supports client-side
cross-origin web resource requests when called using OAuth token
authentication. This is accomplished by using a compatible implementation of
cross-origin resource sharing (CORS). This Web API capability safely works
around browser restrictions imposed to prevent cross-site scripting security
issues. More information:Use OAuth with
Cross-Origin Resource Sharing to connect a Single Page Application to Microsoft
Dynamics CRM
When a user presses keys in a number
or text control, use the new getValue
method to retrieve the value of a control. You can use this value to configure
interactive experiences, such as data validation when a user is typing in a
field, by configuring function handlers for keypress events using the new Keypress
methods- Use addOnKeyPress,
removeOnKeyPress,
and fireOnKeyPress
methods to provide immediate feedback or take actions as user types in a
control. These methods enable you to perform data validations in a control even
before the user commits (saves) the value in a form.
Auto-completion
methods -Use the showAutoComplete
and hideAutoComplete
methods to configure the auto-completion experience in text controls in forms.. These new methods aren’t supported for CRM for phones or
CRM for tablets.
- Web resources and IFRAMEs
- Form script support for new custom controls
- Open records in CRM mobile client with a URL
The ability to create web resources
and IFRAMEs for use with CRM for tablets is now fully supported in all CRM for
tablets forms: iOS, Android, and Windows 10. More information:Create web
resources and IFrame content for use with the CRM for tablets client
Use new custom controls to configure
a visually modern and richer experience for your users in CRM for phones and
CRM for tablets. More information:TechNet: Use the
form editor
The new custom controls support the
same client APIs as the CRM controls, except for the Auto-completion
methods, getValue,
Keypress
methods and Lookup
control methods and events
.
With the new application handler
protocol in Microsoft Dynamics CRM 2016, you can use URLs to directly open
records in CRM for phones and CRM for tablets. You can also open an empty form
for creating an entity record. To use this feature, you have to install CRM for
phones or CRM for tablets on your mobile device.
Query string parameters for the URL
ms-dynamicsxrm://?pagetype=<VALUE>&etn=<VALUE>&id=<VALUE>
Query
string parameter
|
Description
|
pagetype
|
Specify the page type to open.
Valid values are entity, view, dashboard, and create.
This parameter is required.
|
etn
|
Specify the logical name of the
entity for which you want to open or create a record. Logical name of
entities are in lowercase, and defined in the EntityMetadata.LogicalName
property.
This parameter is required if the
pagetype parameter is set to entity, view, or create.
|
id
|
Specify the ID of the entity,
view, or dashboard record that you want to open.
This parameter is required if the
pagetype parameter is set to entity or dashboard.
It is optional if the pagetype
parameter is set to view. If you do not specify the view ID, the
default view for the entity specified in the etn parameter is displayed.
|
Example
Action
|
Example
URL
|
Open an account entity with
account record ID as 91330924-802A-4B0D-A900-34FD9D790829
|
ms-dynamicsxrm://?pagetype=entity&etn=account&id=91330924-802A-4B0D-A900-34FD9D790829
|
Open a view with the view record
ID as 899D4FCF-F4D3-E011-9D26-00155DBA3819 for the contact entity
|
ms-dynamicsxrm://?pagetype=view&etn=contact&id=899D4FCF-F4D3-E011-9D26-00155DBA3819
|
Open a default view for the
account entity
|
ms-dynamicsxrm://?pagetype=view&etn=account
|
Open a dashboard with the
dashboard record ID as 2E3D0841-FA6D-DF11-986C-00155D2E3002
|
ms-dynamicsxrm://?pagetype=dashboard&id=2E3D0841-FA6D-DF11-986C-00155D2E3002
|
Open a form for creating an
account record
|
ms-dynamicsxrm://?pagetype=create&etn=account
|
In addition to rich text, the new KnowledgeArticle
entity supports multimedia data like pictures and videos. Articles have a lifecycle
where they proceed through a publishing workflow.
The FullTextSearchKnowledgeArticleRequest message provides systematic access to a
keyword based search index of the article content. Use this message to access
that search content and provide search results to customers and partners.
To support the knowledge management
capability, new privileges named Publish Knowledge Articles and Approve
Knowledge Articles were added. The Customer Service Representative and
Customer Service Manager roles have these privileges, and a new Knowledge
Manager role has been added.
For the CRM web client, the
client-side form programming API has been updated to include additional
properties in the object returned from the getSelectedResult
function call. All other client APIs and events, which were supported by the
knowledge base search control in the Microsoft Dynamics CRM 2015 release,
continue to be supported.
For the new interactive service hub
client, only the getSearchQuery
and setSearchQuery
methods are supported for the knowledge base search control.
For more information about the
client-side APIs supported by knowledge base search control, see Knowledge base
search control (client-side reference). For more information about
knowledge management, see Knowledge
management entities.
Previously, when an entity was added
to a solution and that solution was exported, the entity and all of its assets
were exported in that solution. This included attributes, forms, views,
relationships, visualizations, and any other assets packaged with the entity.
All objects were exported regardless of whether the developer actually wanted
to ship the object. This process potentially carried dependencies or modified
unintended objects on the target deployment.
Now,a developer or other application
customizer can create and publish solution patches that contain subcomponents
of entities, as compared to publishing the entire entity and all of its assets.
The original solution and multiple released patches can be rolled-up at a later
time into an updated version of the original solution, which then can replace
the original solution.
More information:Create patches to
simplify solution updates.
Service level agreements (SLAs) in
CRM have been enhanced in the current release.
- Manually apply SLAs to incidents (cases): You can now manually apply an SLA to a case by updating the case record, and specifying an active SLA in the new attribute, Incident.ManualSLA, for the case record.
- Programmatically activate or deactivate SLAs: You can now use the UpdateRequest message to activate or deactivate an SLA record. You must activate an SLA record after creating it for the SLA record to be applied to cases. You typically deactivate SLAs during maintenance activities or when you're importing cases and you don't want the SLAs to apply to the cases.
You can also use the UpdateRequest
message to activate and deactivate automatic record creation and update rules
(ConvertRule) and routing rule sets (RoutingRule). This wasn’t
possible in the earlier versions.
The SLA, ConvertRule,
and RoutingRule entities are still for internal use only. Other SDK
messages, except for the Update message, are still not supported for
these entities. More information:Service
entities (contract, incident, knowledge article, queue, calendar,
entitlement, slakpiinstance)
|
You can now create document
templates for Microsoft Excel or Word to have a standardized representation of
your CRM data. These templates can be used by your team members to generate
Excel or Word documents with up-to-date CRM data for analysis and reporting
purposes. Use the SDK to programmatically upload and manage document templates.
More information:Upload and manage
document templates in CRM
Microsoft.Xrm.Tooling.Connector is
the primary interface to CRM for all tooling and Unified Service Desk
operations. It is also provided as part of the Microsoft
Dynamics CRM SDK to developers who want to build CRM connected
Windows applications. Developers can use this updated API to allow the OAuth 2
protocol to be used to authenticate with CRM web services. Adding OAuth enables
multi-factor authentication for improved security and access to CRM.
XRM tooling now also supports
connection strings, which allow for the use of SQL-like connection strings in
the CrmServiceClient
class.
More information:Build Windows
client applications using the XRM tools
The following table lists new
entities included in this release.
Schema
name
|
Display
name
|
Description
|
More
Information
|
KnowledgeArticle
|
Knowledge Article
|
Describes articles that are
organizational knowledge for internal and external use.
|
|
KnowledgeArticleIncident
|
Knowledge Article Incident
|
Contains the associations between
a knowledge article and incident.
|
|
KnowledgeArticleViews
|
Knowledge Article Views
|
Tracks the number of times an
article is viewed per day.
|
|
LanguageLocale
|
Language
|
Contains information about the
supported languages for translating a knowledge article.
|
The following table lists new
messages included in this release.
Request
class
|
Web
API action
|
Description
|
More
information
|
Creates a solution patch from a
managed or unmanaged solution.
|
|||
Creates a new copy of an unmanaged
solution that contains the original solution plus all of its patches.
|
|||
Creates a translation of a
knowledge article record.
|
|||
Creates a major or minor version
of a knowledge article record.
|
|||
Replaces a managed solution plus
all of its patches.
|
|||
N/A
|
Performs a full-text search on
knowledge articles in CRM using the specified search text.
|
||
N/A
|
Increments the per day view count
of a knowledge article record.
|
||
Sets the process that associates
with a given target entity.
|
|||
Updates a component in an
unmanaged solution.
|
The following privileges are new or
changed in this release. For an overall view of how the security role editor
maps to privilege names in this SDK, see Security role UI
to privilege mapping.
Privilege
name
|
Name
displayed in the security role UI
|
More
information
|
prv*AzureServiceConnection
|
Azure Service Connection
|
For internal use only.
|
prv*DataPerformance
|
Data Performance Dashboard
|
|
prv*LanguageLocale
|
Language
|
|
prv*MobileOfflineProfile
|
Mobile Offline Profile
|
For internal use only.
|
prv*RecommendationModel
|
Product Recommendation Model
|
For internal use only.
|
prv*SimilarityRule
|
Similarity Rule
|
For internal use only.
|
prvConfigureSharePoint
|
Run SharePoint Integration Wizard
|
|
prv*KnowledgeArticle
|
Knowledge Article
|
|
prv*KnowledgeArticleViews
|
Knowledge Article Views
|
|
prvApproveKnowledgeArticle
|
Approve Knowledge Articles
|
|
prvPublishKnowledgeArticle
|
Publish Knowledge Articles
|
|
prv*DocumentTemplate
|
Document Template
|
|
prv*PersonalDocumentTemplate
|
Personal Document Template
|
|
prvDocumentGeneration
|
Document Generation
|
|
prv*KnowledgeSearchModel
|
Knowledge Search Model
|
|
prv*TopicModel
|
Topic Model
|
For internal use only.
|
prv*CustomControl
|
Custom Control
|
|
prv*CustomControlDefaultConfig
|
Custom Control Default Config
|
|
prv*CustomControlResource
|
Custom Control Resource
|
* This privilege is one of the
following: Create, Read, Write, Delete, Append, AppendTo, Assign, or Share.
No comments:
Post a Comment