Skip to main content

Goodbye SDK...Hello Developer Guide

With the release of Microsoft Dynamics 365 version 9, we are saying goodbye to the large SDK we are use to downloading to extend Microsoft Dynamics and saying hello to the Developer Guide for Dynamics 365 Customer Engagement.  Here are some highlights with the version 9 release.

1) Previous SDK versions can still be downloaded for previous release of Microsoft Dynamics CRM

2) Per the Developer Guide Dynamics 365 Version 9 is an online only release.

3) To get the early bound generator, plugin registration tool and other CRM tools you will need to use PowerShell and Nuget to get them.  Here is a link provided by Microsoft on how to get these tools.

4) Webhooks have been added to the plugin registration tool.  This allows for easy integration with Azure Functions.

5) As a developer you will have the ability to download the Developer Guide into a PDF for offline viewing.  To do this simply click on the "Download To PDF" on the bottom left of the screen of the Developer Guide.

6) In the previous versions of the SDK, we where provided with sample code to help us quickly get up and running.  To get sample code and projects you will need to check out MSDN and Github.

There is a ton of information in the new Developer Guide and I highly recommend checking it out.  As I go though it, I will be writing posts about specifics in the new Developer Guide.  This post was meant to serve as a high level overview and introduction to the new Developer Guide.
Labels:

Comments

Post a Comment

Popular posts from this blog

Power Pages Update Last Successful Login Using JavaScript and Power Pages API

 Recently while working on a Power Pages implementation for a client, I had the requirement to show the last time a user logged in on their profile page.  I thought this would be easy to do as there is already a field on the contact record for "Last Successful Login" (      adx_identity_lastsuccessfullogin).  This use to update when a user logged in, but it appears Microsoft has removed that automation. While searching I came across a few different ways of achieving this task.  One used application insights in Azure and another one used an HTTP endpoint setup in Power Automate.  I thought, this needs to be simpler.  What I came up with is to use Liquid with JavaScript to tell if a user is logged in or not.  Then use the new Power Pages api to update the logged in users contact record to mark the last time they logged in. Here is the approach I setup: 1) Make sure you turn on the api for contact in Site Settings. 1) Link to Microsoft Do...
100 comments
Read more

Validating User Input In CRM Portals With JavaScript

When we are setting up CRM Portals to allow customers to update their information, open cases, fill out an applications, etc. We want to make sure that we are validating their input before it is committed to CRM.  This way we ensure that our data is clean and meaningful to us and the customer. CRM Portals already has a lot validation checks built into it. But, on occasion we need to add our own.  To do this we will use JavaScript to run the validation and also to output a message to the user to tell them there is an issue they need to fix. Before we can do any JavaScript, we need to check and see if we are using JavaScript on an Entity Form or Web Page.  This is because the JavaScript, while similar, will be different.  First, we will go over the JavaScript for Entity Forms.  Then, we will go over the JavaScript for Web Pages.  Finally, we will look at the notification JavaScript. Entity Form: if (window.jQuery) { (function ($) { if ...
23 comments
Read more

Lookup In Select of URL For Power Pages

 While working on a Power Pages implementation I was consume the Power Pages API to get a Lookup table so I could show and hide information on the form using jQuery.  One issue I was having is I couldn't get a lookup field to return even though I had it as a field in the site setting for the table and included it in the my select statement in the URL.  I kept getting an `unexpected error occurred`. This issue is caused because lookup's are made up using 3 fields. 1) Formatted Value = The information you see in the lookup field (i.e. the record name) 2) Logical Name = The table the related record is a part of 3) Id = The id of the related record In the api there is a 4th field that is returned that is the Associated Navigation Property and it is the logical name of the lookup field. When setting up our select and even saying what columns can be returned in the API, we have to think how the OData endpoint will return the data to us.  ...
3 comments
Read more