Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Analyze Dynamics GP Data in R
Use standard R functions and the development environment of your choice to analyze Dynamics GP data with the CData JDBC Driver for Dynamics GP.
Access Dynamics GP 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 GP and the RJDBC package to work with remote Dynamics GP 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 GP and visualize Dynamics GP 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:
library(RJDBC)
Connect to Dynamics GP as a JDBC Data Source
You will need the following information to connect to Dynamics GP as a JDBC data source:
- Driver Class: Set this to cdata.jdbc.dynamicsgp.DynamicsGPDriver
- 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 GP:
driver <- JDBC(driverClass = "cdata.jdbc.dynamicsgp.DynamicsGPDriver", classPath = "MyInstallationDir\lib\cdata.jdbc.dynamicsgp.jar", identifier.quote = "'")
You can now use DBI functions to connect to Dynamics GP and execute SQL queries. Initialize the JDBC connection with the dbConnect function.
To authenticate set the User and Password connection properties.
To connect set the URL to the Web services endpoint; for example, http://{servername}:{port}/Dynamics/GPService. Additionally, set CompanyId; you can obtain this value in the company setup window: Click Tools -> Setup -> Company.
By default, data summaries are not returned to save performance. Set LookupIds to true to return details such as line items; however, note that entities must be retrieved one at a time.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Dynamics GP JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.dynamicsgp.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:dynamicsgp:CompanyId=mycompanyId;user=myuser;password=mypassword;URL= http://{servername}:{port}/Dynamics/GPService;")
Schema Discovery
The driver models Dynamics GP APIs as relational tables, views, and stored procedures. Use the following line to retrieve the list of tables:
dbListTables(conn)
Execute SQL Queries
You can use the dbGetQuery function to execute any SQL query supported by the Dynamics GP API:
salesinvoice <- dbGetQuery(conn,"SELECT CustomerName, TotalAmount FROM SalesInvoice")
You can view the results in a data viewer window with the following command:
View(salesinvoice)
Plot Dynamics GP Data
You can now analyze Dynamics GP 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(salesinvoice$TotalAmount, main="Dynamics GP SalesInvoice", names.arg = salesinvoice$CustomerName, horiz=TRUE)