<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>node-js on Alexander Development</title><link>https://alexanderdevelopment.net/tag/node-js/</link><description>Recent content in node-js on Alexander Development</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 16 Feb 2017 17:05:52 +0000</lastBuildDate><atom:link href="https://alexanderdevelopment.net/tag/node-js/index.xml" rel="self" type="application/rss+xml"/><item><title>Dynamics 365 and Node.js integration using the Web API - part 2</title><link>https://alexanderdevelopment.net/post/2017/02/16/dynamics-365-and-node-js-integration-using-the-web-api-part-2/</link><pubDate>Thu, 16 Feb 2017 17:05:52 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2017/02/16/dynamics-365-and-node-js-integration-using-the-web-api-part-2/</guid><description>Last year I wrote a post that showed how to retrieve data from a Dynamics 365 Online organization in a Node.js application using the Web API. Today I will share sample code that shows how to update data from a Node.js application using the Web API.
####Updating a single property To update a single property on a record in Dynamics 365, you can make a PUT request to the Web API.</description></item><item><title>Scheduling Dynamics 365 workflows with Azure Functions and Node.js</title><link>https://alexanderdevelopment.net/post/2016/11/25/scheduling-dynamics-365-workflows-with-azure-functions/</link><pubDate>Fri, 25 Nov 2016 17:00:03 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2016/11/25/scheduling-dynamics-365-workflows-with-azure-functions/</guid><description>Earlier this week I showed an easy way to integrate a Node.js application with Dynamics 365 using the Web API. Building on that example, I have created a scheduled workflow runner using Node.js and Azure Functions. Here&amp;rsquo;s how I did it.
First, I created a workflow in Dynamics 365 that creates a note on an account record.</description></item><item><title>Dynamics 365 and Node.js integration using the Web API</title><link>https://alexanderdevelopment.net/post/2016/11/23/dynamics-365-and-node-js-integration-using-the-web-api/</link><pubDate>Wed, 23 Nov 2016 16:17:09 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2016/11/23/dynamics-365-and-node-js-integration-using-the-web-api/</guid><description>I wrote a blog post in early 2015 that showed how to access the Dynamics CRM organization data service from a Node.js application. Today I will show an easy way to retrieve data from a Dynamics 365 Online organization in a Node.js application using the Web API.
Unlike the CRM organization service, the Dynamics 365 Web API does not allow you to authenticate directly with a user name and password.</description></item><item><title>Dynamics CRM and the Internet of Things - part 5</title><link>https://alexanderdevelopment.net/post/2016/01/18/dynamics-crm-and-the-internet-of-things-part-5/</link><pubDate>Mon, 18 Jan 2016 22:17:57 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2016/01/18/dynamics-crm-and-the-internet-of-things-part-5/</guid><description>This is the fifth and final post in a five-part series on how I integrated a Raspberry Pi with Microsoft Dynamics CRM to recognize contacts using automobile license plates. Although the code samples are focused on license plate recognition, the solution architecture I used is applicable to any Dynamics CRM + Internet of Things (IoT) integration.</description></item><item><title>Dynamics CRM and the Internet of Things - part 4</title><link>https://alexanderdevelopment.net/post/2016/01/11/dynamics-crm-and-the-internet-of-things-part-4/</link><pubDate>Mon, 11 Jan 2016 13:38:49 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2016/01/11/dynamics-crm-and-the-internet-of-things-part-4/</guid><description>This is the fourth post in a five-part series on how I integrated a Raspberry Pi with Microsoft Dynamics CRM to recognize contacts using automobile license plates. Although the code samples are focused on license plate recognition, the solution architecture I used is applicable to any Dynamics CRM + Internet of Things (IoT) integration.</description></item><item><title>Dynamics CRM and the Internet of Things - part 3</title><link>https://alexanderdevelopment.net/post/2016/01/03/dynamics-crm-and-the-internet-of-things-part-3/</link><pubDate>Sun, 03 Jan 2016 23:19:06 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2016/01/03/dynamics-crm-and-the-internet-of-things-part-3/</guid><description>This is the third post in a five-part series on how I integrated a Raspberry Pi with Microsoft Dynamics CRM to recognize contacts using automobile license plates. Although the code samples are focused on license plate recognition, the solution architecture I used is applicable to any Dynamics CRM + Internet of Things (IoT) integration.</description></item><item><title>Dynamics CRM and the Internet of Things - part 2</title><link>https://alexanderdevelopment.net/post/2015/12/21/dynamics-crm-and-the-internet-of-things-part-2/</link><pubDate>Mon, 21 Dec 2015 16:50:02 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2015/12/21/dynamics-crm-and-the-internet-of-things-part-2/</guid><description>This is the second post in a five-part series on how I integrated a Raspberry Pi with Microsoft Dynamics CRM to recognize contacts using automobile license plates. As I mentioned in the first post of the series, the solution architecture I used is applicable to any Dynamics CRM + Internet of Things (IoT) integration.</description></item><item><title>Dynamics CRM and the Internet of Things - part 1</title><link>https://alexanderdevelopment.net/post/2015/12/14/dynamics-crm-and-the-internet-of-things-part-1/</link><pubDate>Mon, 14 Dec 2015 16:02:17 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2015/12/14/dynamics-crm-and-the-internet-of-things-part-1/</guid><description>Today&amp;rsquo;s post is the first in a five-part series on how I integrated a Raspberry Pi with Microsoft Dynamics CRM to recognize contacts using automobile license plates. Although my solution is focused on the use of license plate numbers captured by a webcam, the solution architecture is applicable to any Dynamics CRM + Internet of Things (IoT) integration.</description></item><item><title>Using RabbitMQ as a message broker in Dynamics CRM data interfaces – part 5</title><link>https://alexanderdevelopment.net/post/2015/01/27/using-rabbitmq-as-a-message-broker-in-dynamics-crm-data-interfaces-part-5/</link><pubDate>Tue, 27 Jan 2015 18:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2015/01/27/using-rabbitmq-as-a-message-broker-in-dynamics-crm-data-interfaces-part-5/</guid><description>This the final post in my five-part series on creating loosely coupled data interfaces for Dynamics CRM using RabbitMQ. In part 3 and part 4 I showed two approaches for building a Dynamics CRM plug-in that publishes notification messages to a RabbitMQ exchange. In today’s post I will show how to create a Windows console application that reads messages from a queue and writes the data to Dynamics CRM.</description></item><item><title>Authenticating from a Node.js client to Dynamics CRM via AD FS and OAuth2</title><link>https://alexanderdevelopment.net/post/2015/01/24/authenticating-from-a-node-js-client-to-dynamics-crm-via-ad-fs-and-oauth2/</link><pubDate>Sat, 24 Jan 2015 00:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2015/01/24/authenticating-from-a-node-js-client-to-dynamics-crm-via-ad-fs-and-oauth2/</guid><description>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.</description></item><item><title>Using RabbitMQ as a message broker in Dynamics CRM data interfaces – part 4</title><link>https://alexanderdevelopment.net/post/2015/01/22/using-rabbitmq-as-a-message-broker-in-dynamics-crm-data-interfaces-part-4/</link><pubDate>Thu, 22 Jan 2015 18:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2015/01/22/using-rabbitmq-as-a-message-broker-in-dynamics-crm-data-interfaces-part-4/</guid><description>Welcome back to my five-part series on creating loosely coupled data interfaces for Dynamics CRM using RabbitMQ. In my last post I showed how to build a Dynamics CRM plug-in that publishes notification messages to a RabbitMQ exchange using the official RabbitMQ .Net client library. Unfortunately, that plug-in can’t successfully communicate with a RabbitMQ server if it’s executed inside the Dynamics CRM sandbox, so in today’s post I will show how to achieve the same results with a sandboxed plug-in.</description></item><item><title>Using RabbitMQ as a message broker in Dynamics CRM data interfaces – part 3</title><link>https://alexanderdevelopment.net/post/2015/01/20/using-rabbitmq-as-a-message-broker-in-dynamics-crm-data-interfaces-part-3/</link><pubDate>Tue, 20 Jan 2015 18:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2015/01/20/using-rabbitmq-as-a-message-broker-in-dynamics-crm-data-interfaces-part-3/</guid><description>This is the third post of a five-part series on creating loosely coupled data interfaces for Dynamics CRM using RabbitMQ. Last time I showed how to install and configure a RabbitMQ server to support passing messages to and from Dynamics CRM. Today I will show how to build a Dynamics CRM plug-in that publishes notification messages to a RabbitMQ exchange using the official RabbitMQ .</description></item><item><title>Using RabbitMQ as a message broker in Dynamics CRM data interfaces – part 2</title><link>https://alexanderdevelopment.net/post/2015/01/14/using-rabbitmq-as-a-message-broker-in-dynamics-crm-data-interfaces-part-2/</link><pubDate>Wed, 14 Jan 2015 18:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2015/01/14/using-rabbitmq-as-a-message-broker-in-dynamics-crm-data-interfaces-part-2/</guid><description>Welcome back to this five-part series on creating loosely coupled data interfaces for Dynamics CRM using RabbitMQ. In my last post I discussed why you would want to incorporate a message broker into your Dynamics CRM data interfaces, and today I will show how to install and configure RabbitMQ to support the examples I’ll be presenting in the rest of the series.</description></item><item><title>Using RabbitMQ as a message broker in Dynamics CRM data interfaces – part 1</title><link>https://alexanderdevelopment.net/post/2015/01/12/using-rabbitmq-as-a-message-broker-in-dynamics-crm-data-interfaces-part-1/</link><pubDate>Mon, 12 Jan 2015 18:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2015/01/12/using-rabbitmq-as-a-message-broker-in-dynamics-crm-data-interfaces-part-1/</guid><description>One of the things I love about Dynamics CRM is how easy it is to create data interfaces to enable integration with other systems. If you’ve worked with Dynamics CRM for any length of time, you’ve probably seen multiple web service integrations that enable interoperability with other line-of-business and legacy systems.</description></item><item><title>Creating a near real-time streaming interface for Dynamics CRM with Node.js – part 4</title><link>https://alexanderdevelopment.net/post/2014/12/11/creating-a-near-real-time-streaming-interface-for-dynamics-crm-with-node-js-part-4/</link><pubDate>Thu, 11 Dec 2014 18:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2014/12/11/creating-a-near-real-time-streaming-interface-for-dynamics-crm-with-node-js-part-4/</guid><description>This is the final post in my four-part series about creating a near real-time streaming interface for Microsoft Dynamics CRM using Node.js and Socket.IO. In my last post I showed how to write the plug-in code to send messages from CRM to the Node.js application. In today’s post I will show how to configure a client to receive and process notifications from the Node.</description></item><item><title>Creating a near real-time streaming interface for Dynamics CRM with Node.js – part 3</title><link>https://alexanderdevelopment.net/post/2014/12/09/creating-a-near-real-time-streaming-interface-for-dynamics-crm-with-node-js-part-3/</link><pubDate>Tue, 09 Dec 2014 18:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2014/12/09/creating-a-near-real-time-streaming-interface-for-dynamics-crm-with-node-js-part-3/</guid><description>This is the third post in my four-part series about creating a near real-time streaming interface for Microsoft Dynamics CRM using Node.js and Socket.IO. In my last post I showed how to create the Node.js component of the solution to process messages received from Dynamics CRM and send notifications to connected clients.</description></item><item><title>Creating a near real-time streaming interface for Dynamics CRM with Node.js – part 2</title><link>https://alexanderdevelopment.net/post/2014/12/05/creating-a-near-real-time-streaming-interface-for-dynamics-crm-with-node-js-part-2/</link><pubDate>Fri, 05 Dec 2014 18:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2014/12/05/creating-a-near-real-time-streaming-interface-for-dynamics-crm-with-node-js-part-2/</guid><description>This is the second post in my four-part series about creating a near real-time streaming interface for Microsoft Dynamics CRM using Node.js and Socket.IO. In my last post I presented an overview of how a near real-time streaming interface can be used with Dynamics CRM, and I discussed the solution approach.</description></item><item><title>Creating a near real-time streaming interface for Dynamics CRM with Node.js – part 1</title><link>https://alexanderdevelopment.net/post/2014/12/03/creating-a-near-real-time-streaming-interface-for-dynamics-crm-with-node-js-part-1/</link><pubDate>Wed, 03 Dec 2014 18:00:00 +0000</pubDate><guid>https://alexanderdevelopment.net/post/2014/12/03/creating-a-near-real-time-streaming-interface-for-dynamics-crm-with-node-js-part-1/</guid><description>Welcome to a four-part series about creating a near real-time streaming interface for Microsoft Dynamics CRM using Node.js and Socket.IO.
In today’s post I will present an overview of how a near real-time streaming interface can be used with Dynamics CRM, and I will discuss the solution approachIn the second post, I will show how to create the Node.</description></item></channel></rss>