OAuth authentication, especially involving the Common Data Service or Dynamics 365, is a subject you may not grasp fully the first time around. The technical setup required can be tricky to understand or even implement at all, meaning you find yourself dealing with error codes such as AADSTS65001.
Developers typically get the short end of the stick in lots of things, and consistent learning tools is one area I’d highlight, particularly in the Dynamics 365 space. Fortunately, this no longer appears to be the case, thanks to the release of exam MB-400.
Custom pricing is an invaluable feature within Dynamics 365 Customer Engagement, that can be used to fine-tune your sales processes. If you're interested in finding out more about them, then my latest tutorial video is for you - find out more in this post!
Project Service Automation (PSA) can be a beast when first approached. The application contains a breadth of functionality which is not always properly documented and can be challenging to figure out. To find proof of this assertion, we only need to look at how price list mark-ups and discounts operate.
It seems to be non-stop changes and announcements when it comes to licensing for Dynamics 365 Customer Engagement at the moment. Now, as we move into September, we get yet another, which informs us of some potentially troublesome API limits, that will take effect from October onwards.
Having the ability to straightforwardly obtain a records Globally Unique Identifier after programmatically creating it within Dynamics 365 Customer Engagement can help significantly with data integration requirements. This is a relatively easy task when working with the Web API using JScript but less so if C# is your language of choice...
By default, the Dynamics 365 Customer Engagement connector for Azure Data Factory V2 exposes a predefined list of fields, that must have data mapped to them for any Copy Data task to complete successfully. This behaviour can be impractical depending on your particular scenario; fortunately, there is a way in which you can override this.
Feature deprecations can often cause some degree of disruption, especially if they involve custom code. Microsoft has recently deprecated the Xrm.Page object for JScript form functions in Dynamics 365 Customer Engagement. Find out more about this change and what you will need to do to fix this as part of this week's blog post.
Azure Data Factory V2 not just has 1, but three separate connectors that all claim to hook up to Dynamics 365 Customer Engagement/Dynamics CRM! So which connector is the "right" one to use and what differences do they have? With a little help from Alan Partridge, we can clear up any confusion...
A few years ago on the blog, we saw how it was possible to utilise Fetch XML queries within Power BI. Things have moved on since then and, thanks to the awesome Dynamics community, there is now a way of getting around the issues highlighted in the original post...