Ready to get started?

Download a free trial of the Dynamics 365 Driver to get started:

 Download Now

Learn more:

Dynamics 365 Icon Dynamics 365 JDBC Driver

Rapidly create and deploy powerful Java applications that integrate with Dynamics 365.

Analyze Dynamics 365 Data in R

Use standard R functions and the development environment of your choice to analyze Dynamics 365 data with the CData JDBC Driver for Dynamics 365.

Access Dynamics 365 data with pure R script and standard SQL on any machine where R and Java can be installed. You can use the CData JDBC Driver for Dynamics 365 and the RJDBC package to work with remote Dynamics 365 data in R. By using the CData Driver, you are leveraging a driver written for industry-proven standards to access your data in the popular, open-source R language. This article shows how to use the driver to execute SQL queries to Dynamics 365 and visualize Dynamics 365 data by calling standard R functions.

Install R

You can match the driver's performance gains from multi-threading and managed code by running the multithreaded Microsoft R Open or by running open R linked with the BLAS/LAPACK libraries. This article uses Microsoft R Open 3.2.3, which is preconfigured to install packages from the Jan. 1, 2016 snapshot of the CRAN repository. This snapshot ensures reproducibility.

Load the RJDBC Package

To use the driver, download the RJDBC package. After installing the RJDBC package, the following line loads the package:


Connect to Dynamics 365 as a JDBC Data Source

You will need the following information to connect to Dynamics 365 as a JDBC data source:

  • Driver Class: Set this to cdata.jdbc.dynamics365.Dynamics365Driver
  • Classpath: Set this to the location of the driver JAR. By default this is the lib subfolder of the installation folder.

The DBI functions, such as dbConnect and dbSendQuery, provide a unified interface for writing data access code in R. Use the following line to initialize a DBI driver that can make JDBC requests to the CData JDBC Driver for Dynamics 365:

driver <- JDBC(driverClass = "cdata.jdbc.dynamics365.Dynamics365Driver", classPath = "MyInstallationDir\lib\cdata.jdbc.dynamics365.jar", identifier.quote = "'")

You can now use DBI functions to connect to Dynamics 365 and execute SQL queries. Initialize the JDBC connection with the dbConnect function.

Edition and OrganizationUrl are required connection properties. The Dynamics 365 connector supports connecting to the following editions: CustomerService, FieldService, FinOpsOnline, FinOpsOnPremise, HumanResources, Marketing, ProjectOperations and Sales.

For Dynamics 365 Business Central, use the separate Dynamics 365 Business Central driver.

OrganizationUrl is the URL to your Dynamics 365 organization. For instance,

Built-in Connection String Designer

For assistance in constructing the JDBC URL, use the connection string designer built into the Dynamics 365 JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

java -jar cdata.jdbc.dynamics365.jar

Fill in the connection properties and copy the connection string to the clipboard.

Below is a sample dbConnect call, including a typical JDBC connection string:

conn <- dbConnect(driver,"jdbc:dynamics365:OrganizationUrl=;Edition=Sales;InitiateOAuth=GETANDREFRESH")

Schema Discovery

The driver models Dynamics 365 APIs as relational tables, views, and stored procedures. Use the following line to retrieve the list of tables:


Execute SQL Queries

You can use the dbGetQuery function to execute any SQL query supported by the Dynamics 365 API:

goalheadings <- dbGetQuery(conn,"SELECT GoalHeadingId, Name FROM GoalHeadings WHERE Name = 'MyAccount'")

You can view the results in a data viewer window with the following command:


Plot Dynamics 365 Data

You can now analyze Dynamics 365 data with any of the data visualization packages available in the CRAN repository. You can create simple bar plots with the built-in bar plot function:

par(las=2,ps=10,mar=c(5,15,4,2)) barplot(goalheadings$Name, main="Dynamics 365 GoalHeadings", names.arg = goalheadings$GoalHeadingId, horiz=TRUE)