1. Sneak Peek Microsoft Dynamics CRM 2016 SDK
Aileen Gusni
10th December 2015

2. Supported by:

3. Introduction Presenter name is Aileen Gusni
Implementing CRM since CRM 4.0
Currently working in Singapore
Active Community Contributor
Active Blogger:
Other info can just ask herself…

4. Agenda Brief introduction : Microsoft Dynamics CRM 2016
Focus: What’s new for Developer?

5. What’s new for Developer: At a Glance
All the CRM Online Features from the CRM 2015 Update 1 so-called “Carina” now available for CRM 2016, except: Parature Integration
Web API & CORS for Integration Usage
New Entities in CRM 2016
New Messages in CRM 2016
New Form Scripting Capabilities
Solution Enhancement

6. Highlighted Keys for CRM 2015 Update 1
Alternate Keys & Upsert Operation
Change Tracking & Plugin Trace Log
New Query Clause: Older Than …
Record Creation & Update Rules for Incoming Activities
Trigger Custom Action from Workflow/Dialog
User Mapping with SharePoint
Folder Level Tracking
Form Enhancement: Open Quick Create Form, Turbo Form
Alternate Keys: Easier for Integration
Thinking to have more than 1 field as unique key? GUID only as the key is now not your problem
Support for additional “older than” clauses for date and time fields in FetchXML and QueryExpression
Until the previous release of CRM, you could only query for dates "Older Than X Months" using FetchXML and QueryExpression. This limited the ability to find past cases with other granularity levels (hours, days, weeks, and so on), for example, finding urgent cases older than 15 minutes.
The following settings for the "older than" clause are added in FetchXML and QueryExpression that will help you to find the cases using various granularity levels:
Older Than X Minutes
Older Than X Hours
Older Than X Days
Older Than X Weeks
Older Than X Years

7. Web API & CORS for Integration Usage
The Web API will make it easier to create applications across a wide variety of platforms, devices, and programming languages
No need to download any Microsoft Dynamics CRM SDK assemblies
Easy, just enable from System Setting
organization name>.crm.dynamics.com/api/data

8. New Entities in CRM 2016
It has all entities from CRM 2015 & CRM 2015 Update 1, such as:
Theme, Office Document, Plugin Trace Log, User Mapping
Additional New Entities, related to the enhanced Knowledge Base Article, such as:
Knowledge Article & Language Locale
Because we are expecting the new Look & Feel of Knowledge Base:
New Life Cycle, Associate to Entity, Versioning, View Count, and of course TRANSLATION supported!
New KB Life Cycle:
0: Draft (after a knowledge article is created)
1: Approved (after a knowledge article is approved)
2: Scheduled (after a knowledge article is scheduled to be published)
3: Published (after a knowledge article is published)
4: Expired (after a knowledge article is expired as per the expiration date specified while publishing)
5: Archived (after a knowledge article is archived)
6: Discarded (after a knowledge article is discarded)

9. New Messages in CRM 2016
It has all entities from CRM 2015 & CRM 2015 Update 1, such as:
ApplyRecordCreationAndUpdateRuleRequest,
ExecuteTransactionRequest,
PublishThemeRequest,
RetrieveEntityChangesRequest,
UpsertRequest

10. New Messages in CRM 2016 Request class name Web API action Description
CloneAsPatchRequest
CloneAsPatch Action
Creates a solution patch from a managed or unmanaged solution.
CloneAsSolutionRequest
CloneAsSolution Action
Creates a new copy of an unmanaged solution that contains the original solution plus all of its patches.
CreateKnowledgeArticleTranslationRequest
CreateKnowledgeArticleTranslation Action
Creates a translation of a knowledge article record.
CreateKnowledgeArticleVersionRequest
CreateKnowledgeArticleVersion Action
Creates a major or minor version of a knowledge article record.
DeleteAndPromoteRequest
DeleteAndPromote Action
Replaces a managed solution plus all of its patches.
FullTextSearchKnowledgeArticleRequest
N/A
Performs a full-text search on knowledge articles in CRM using the specified search text.
IncrementKnowledgeArticleViewCountRequest
Increments the per day view count of a knowledge article record.
SetProcessRequest
SetProcess Action
Sets the process that associates with a given target entity.
UpdateSolutionComponentRequest
UpdateSolutionComponent Action
Updates a component in an unmanaged solution.

11. New Form Scripting Capabilities - 1
Now you can write scripts for Subgrid in supported Way (introduced in CRM 2015 Update 1)
Open Quick Create Form on demand
Get Show Time
Get Form Factor, whether you want to check this client is using which device?

12. New Form Scripting Capabilities - 2
New Custom Control Methods introduced in CRM 2016!!
Keypress Method, get immediate feedback as user types in something in a CRM Form Control
Get Value, gets the latest value in a control as the user types characters in a specific text or number field. This method helps you to build interactive experiences by validating data and alerting users as they type characters in a control.
Now, you don’t need the users to complete their typing activity by waiting them to press tab or change to another field
Keypress Method:
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.

13. New Form Scripting Capabilities - 3
Auto Complete in CRM Form Control!!
You don’t need to put all as lookup field/option set anymore
It helps you to ‘Suggest the Users’

14. Solution Enhancement
A new solution capability is now available that allows a developer or other application customizer to create solution patches that contain subcomponents of entities, as compared to publishing the entire entity and all of its assets.
These assets include attributes, forms, views, relationships, and visualizations, and any other assets that are packaged with the entity
Solution enhancements
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.
A new solution capability is now available that allows a developer or other application customizer to create 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.

15. Solution Enhancement – Understand Patch
You can export solutions with selected entity assets, such as entity fields, forms, and views, rather than entire entities with all the assets. To create the segmented solutions and patches, you can use the CRM user interface, without writing code
Solution enhancements
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.
A new solution capability is now available that allows a developer or other application customizer to create 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.

16. Patch Example Patch name Description
SolutionA, version 1.0 (unmanaged)
Contains entityA with 6 fields.
SolutionA, version (unmanaged)
Contains entityA with 3 fields ( -3 ) and adds entityB with 10 fields.
SolutionA, version (unmanaged)
Contains entityC with 10 fields.
Solution enhancements
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.
A new solution capability is now available that allows a developer or other application customizer to create 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.

17. Result
The developer or customizer first imports the base solution (SolutionA 1.0) into the organization. The result is entityA with 6 fields in the organization.
Next, the SolutionA patch is imported. The organization now contains entityA with 3 fields plus entityB with 10 fields.
Finally, SolutionA patch is imported. The organization now contains entityA with 3 fields, entityB with 10 fields, plus entityC with 10 fields.
So you can just add the asset selectively and also you can remove it like what we did for the entity 9from 6 to 3 fields) -> -3 Fields Changed
Solution enhancements
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.
A new solution capability is now available that allows a developer or other application customizer to create 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.

18. References & Further Reading
Official MSDN Links
us/library/gg309589(v=crm.7).aspx#BKMK_NewInSpring2015
You can download the SDK Now

19. Now, what are you waiting for?
Read more about Dynamics CRM
Learn the Licensing Guide
Sign Up or Download the Microsoft Dynamics CRM Trial
Contact & Engage with us as Microsoft Gold Partners
Start Your Dynamics Journey Now…

20. Q & A