Articles in this section

See more

Office 365 Connector

  • Updated
Follow
  • Starter
  • Business
  • Enterprise
  • On-Premise
  • Add-on

Overview

Office 365 connector allows the fastest and easiest way to connect to real-time Office 365 data. The connector works just like any other connector for connected app.

Etlworks partnered with CData to provide access to Office 365 using industry-standard JDBC protocol. Read about CData Office 365 JDBC connector.

When to use Office 365 connector

Use this connector to create Flows that extract data and load data into Office 365.

Prerequisites

Enable the Office 365 connector for your Etlworks account. Contact support@etlworks.com to enable the connector.

Create a Connection

Here's how you can create a Connection in two easy steps:

Step 1. In the Connections window, click +, and type in office 365.

mceclip0.png

Step 2. Enter Connection parameters:

  • Permissions: select the permissions that will be used to access Office 365 data. 
  • OAuth Token: sign in with Microsoft.

mceclip2.png

Use Other parameters to specify the Connection string options. Read about available Connection string options.

mceclip1.png

Work with Office 365

Office 365 Data Models

The connector models the Office 365 API as relational tables. Any changes to the remote data are immediately reflected in your queries; the table definitions are dynamically retrieved. When you connect, the driver connects to Office 365 and gets the list of tables and the metadata for the tables by calling the appropriate Web services.

API limitations and requirements are documented in this section; you can use the SupportEnhancedSQL feature, set by default to circumvent most of these limitations.

Read about the data model.

Stored procedures

Stored procedures are available to complement the data available from the Data Model. It may be necessary to update data available from a view using a stored procedure because the data does not provide for direct, table-like, two-way updates. In these situations, the data retrieval is done using the appropriate view or table, while the update is done by calling a stored procedure. Stored procedures take a list of parameters and return a dataset that contains the collection of tuples that constitute the response.

Read about available stored procedures in the data model.  

To call stored procure from the SQL Flow or Before/After SQL, use EXEC sp_name params=value. Example:

EXECUTE my_proc @second = 2, @first = 1, @third = 3;

SQL Compliance

The connector supports several operations on data, including querying, deleting, modifying, and inserting.

Read about SQL Compliance.

Extract data from Office 365

Note: Extracting data from Office 365 is similar toextracting data from the relational database.

Here are the steps on extracting data from Office 365:

Step 1. Create Office 365 Connection which will be used as a source (FROM).

Step 2. Create a destination Connection, for example, a Connection to the relational database, and if needed, a Format (Format is not needed if the destination is a database or well-known API).

Step 3. Create a Flow where the source is a connected app, and the destination is a Connection created in step 2, for example, a relational database.

Step 4. Add a new source-to-destination transformation.

Step 5. Select the Office 365 Connection created in step 1 as a source Connection and select the data object you are extracting data from.

Step 6. Select TO Connection, Format (if needed), and object (for example, database table) to load data into.

Step 7. Click MAPPING and optionally enter Source query (you don't need a query if you are extracting data from the Office 365 data object unconditionally).

Step 8. Optionally define the per-field Mapping.

salesforce-mapping.png

Step 9. Add more transformations if needed.

Load data in Office 365

Note: Loading data in Office 365 is similar toloading data into a relational database.

Here are the steps on loading data in Office 365:

Step 1. Create a source Connection and a Format (if needed).

Step 2. Create a destination Office 365 Connection.

Step 3. Create a Flow where the destination is a connected app.

Step 4. Add new source-to-destination transformation.

Step 5. Select FROM and TO Connections and objects (also a FROM Format if needed).

Step 6. Optionally define the per-field Mapping.

Step 7. Add more transformations if needed.

Browse data in Office 365

You must have an Office 365 Connection to browse objects and run SQL queries.

Use the Etlworks Explorer to browse data and metadata in Office 365 as well as execute DML and SELECT queries against the Office 365 Connection.

Related articles