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...
The importance of segregated deployment environments for any IT application cannot be understated. Even if this only comprises of a single test/User Acceptance Testing (UAT) environment, there are a plethora of benefits involved, which should easily outweigh any administrative or time effort involved: They provide a safe "sandbox" for any functionality or developmental changes to be [...]
Earlier this month, a colleague escalated an issue to me involving Dynamics CRM/365 Customer Engagement (CRM/D365CE), specifically relating to email tracking. This feature is by far one of the most useful and unwieldy within the application, if not configured correctly. In days of yore, the setup steps involved could be tedious to implement, mainly if [...]
I've gone on record previously saying how highly I rate the Dynamics CRM/Dynamics 365 Customer Engagement (CRM/D365CE) community. Out of all the groups I have been a part of in the past, you couldn't ask for a more diverse, highly passionate and - most importantly of all - helpful community. There are a lot of [...]
UPDATE 02/09/2018: It turns out that there is a far better way of fixing this problem. Please click here to find out more. I thought I was losing my mind the other day. This feeling can be a general occurrence in the world of IT, when something completely random and unexplainable happens - emphasised even [...]