Build Microsoft Planner-Connected ETL Processes in Google Data Fusion

Google Data Fusion allows users to perform self-service data integration to consolidate disparate data. Uploading the CData JDBC Driver for Microsoft Planner enables users to access live Microsoft Planner data from within their Google Data Fusion pipelines. While the CData JDBC Driver enables piping Microsoft Planner data to any data source natively supported in Google Data Fusion, this article walks through piping data from Microsoft Planner to Google BigQuery,

Upload the CData JDBC Driver for Microsoft Planner to Google Data Fusion

Upload the CData JDBC Driver for Microsoft Planner to your Google Data Fusion instance to work with live Microsoft Planner data. Due to the naming restrictions for JDBC drivers in Google Data Fusion, create a copy or rename the JAR file to match the following format driver-version.jar. For example: cdatamicrosoftplanner-2020.jar

1. Open your Google Data Fusion instance
2. Click the to add an entity and upload a driver
3. On the "Upload driver" tab, drag or browse to the renamed JAR file.
4. On the "Driver configuration" tab:
   • Name: Create a name for the driver (cdata.jdbc.microsoftplanner) and make note of the name
   • Class name: Set the JDBC class name: (cdata.jdbc.microsoftplanner.MicrosoftPlannerDriver)
5. Click "Finish"

Connect to Microsoft Planner Data in Google Data Fusion

With the JDBC Driver uploaded, you are ready to work with live Microsoft Planner data in Google Data Fusion Pipelines.

1. Navigate to the Pipeline Studio to create a new Pipeline
2. From the "Source" options, click "Database" to add a source for the JDBC Driver
3. Click "Properties" on the Database source to edit the properties

   NOTE: To use the JDBC Driver in Google Data Fusion, you will need a license (full or trial) and a Runtime Key (RTK). For more information on obtaining this license (or a trial), contact our sales team.

   • Set the Label
   • Set Reference Name to a value for any future references (i.e.: cdata-microsoftplanner)
   • Set Plugin Type to "jdbc"
   • Set Connection String to the JDBC URL for Microsoft Planner. For example:
     
     jdbc:microsoftplanner:RTK=5246...;OAuthClientId=MyApplicationId;OAuthClientSecret=MySecretKey;CallbackURL=http://localhost:33333;InitiateOAuth=GETANDREFRESH;

     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.

     java -jar cdata.jdbc.microsoftplanner.jar

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

   • Set Import Query to a SQL query that will extract the data you want from Microsoft Planner, i.e.:
     SELECT * FROM Tasks
4. From the "Sink" tab, click to add a destination sink (we use Google BigQuery in this example)
5. Click "Properties" on the BigQuery sink to edit the properties
   • Set the Label
   • Set Reference Name to a value like microsoftplanner-bigquery
   • Set Project ID to a specific Google BigQuery Project ID (or leave as the default, "auto-detect")
   • Set Dataset to a specific Google BigQuery dataset
   • Set Table to the name of the table you wish to insert Microsoft Planner data into

With the Source and Sink configured, you are ready to pipe Microsoft Planner data into Google BigQuery. Save and deploy the pipeline. When you run the pipeline, Google Data Fusion will request live data from Microsoft Planner and import it into Google BigQuery.

While this is a simple pipeline, you can create more complex Microsoft Planner pipelines with transforms, analytics, conditions, and more. Download a free, 30-day trial of the CData JDBC Driver for Microsoft Planner and start working with your live Microsoft Planner data in Google Data Fusion today.