Toward the end of last year, I put together a collection of code for using RabbitMQ as a message broker with Dynamics CRM data interfaces, and I published to my my public CRM sample code repository on GitHub here.
Last week I decided to finally take a look at using OAuth2 as an authentication protocol with Dynamics CRM. I wanted to understand how it could enable non-Windows clients to consume CRM data. As it turns out, I was unable to find any documentation or comprehensive code samples for non-Windows clients, so I put together my own Node.js client, and I've added the code to my Crm-Sample-Code repository on GitHub here: https://github.com/lucasalexander/Crm-Sample-Code/tree/master/NodeClientDemo. Having endured a lot of frustration in getting this to work, I'd like to share some additional notes that might be helpful if you decide to start using OAuth2 with CRM.
When Dynamics CRM 2013 was released, I thought access teams were the new killer feature in that version, and I even developed custom workflow activity code to make managing access team membership easier by using connection records. I have thus far not had an opportunity to use access teams in a real project, so I was disappointed to read this blog post by Ben Hosking (AKA "The Hosk") about how Microsoft doesn't provide any out-of-the-box capabilities for moving access team templates between Dynamics CRM organizations. In that post, the Hosk says, "It’s possible someone could build a console app to import the access team templates but as yet no one has created it." Challenge accepted.
Last month I put together a proof-of-concept solution that showed how to create a near real-time streaming interface for Microsoft Dynamics CRM using Node.js and Socket.IO.
Over the years, I've shared a lot of code as part of my blogging, but I didn't do a particularly good job of making the code easily available outside of the individual blog posts. I also realized I didn't even have all the code where I could easily get to it from my PC!
I've been using the completely awesome XrmToolBox to import translations for a large CRM organization, but I kept running into System.TimeoutException errors like the following:
System.TimeoutException: The HTTP request to 'https://XXX/XrmServices/2011/Organization.svc' has exceeded the allotted timeout of 00:02:00. The time allotted to this operation may have been a portion of a longer timeout.
I've posted a new entry on the HP Enterprise Services Application Services blog that is the third item in a three-part series about how to use HP IDOL OnDemand for integrated text analysis inside Microsoft Dynamics CRM. This post shows how to index CRM data and use IDOL OnDemand's find similar API to search for relevant records.
I've posted a new entry on the HP Enterprise Services Application Services blog that is the second item in a three-part series about how to use HP IDOL OnDemand for integrated text analysis inside Microsoft Dynamics CRM. This post shows to calculate sentiment (positive/neutral/negative) of emails in CRM using the IDOL OnDemand sentiment analysis API.
I've posted a new entry on the HP Enterprise Services Application Services blog that is the first item in a three-part series about how to use HP IDOL OnDemand for integrated text analysis inside Microsoft Dynamics CRM.
I've posted a new entry on the HP Enterprise Services Application Services blog that shows how to run the out-of-the-box CRM 2013 PowerShell cmdlets from a remote system.