Analyze Microsoft Planner Data in R

Access Microsoft Planner 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 Microsoft Planner and the RJDBC package to work with remote Microsoft Planner 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 Microsoft Planner and visualize Microsoft Planner 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 Microsoft Planner as a JDBC Data Source

You will need the following information to connect to Microsoft Planner as a JDBC data source:

• Driver Class: Set this to cdata.jdbc.microsoftplanner.MicrosoftPlannerDriver
• 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 Microsoft Planner:

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

You can connect without setting any connection properties for your user credentials. Below are the minimum connection properties required to connect.

• InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
• Tenant (optional): Set this if you wish to authenticate to a different tenant than your default. This is required to work with an organization not on your default Tenant.

When you connect the Driver opens the MS Planner OAuth endpoint in your default browser. Log in and grant permissions to the Driver. The Driver then completes the OAuth process.

1. Extracts the access token from the callback URL and authenticates requests.
2. Obtains a new access token when the old one expires.
3. Saves OAuth values in OAuthSettingsLocation to be persisted across connections.

Built-in Connection String Designer

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

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:

Schema Discovery

The driver models Microsoft Planner 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 Microsoft Planner API:

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

Plot Microsoft Planner Data

You can now analyze Microsoft Planner 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: