Microsoft Exchange Ingestion Source

See the Connector Marketplace topic. Please request your administrator to start a trial or subscribe to the Premium Microsoft Exchange connector.

In Gathr, it can be added as a channel to help in fetching customers’ and prospects’ data and transform it as needed before storing it in a desired data warehouse to run further analytics.

Data Source Configuration #

Configure the data source parameters as explained below.

Fetch From Source/Upload Data File #

To design the application, you can either fetch the sample data from the Microsoft Exchange source by providing the data source connection details or upload a sample data file in one of the supported formats to see the schema details during the application design phase.

Upload Data File #

To design the application, please upload a data file containing sample records in a format supported by Gathr.

The sample data provided for application design should match the data source schema from which data will be fetched during runtime.

If Upload Data File method is selected to design the application, provide the below details.

File Format #

Select the format of the sample file depending on the file type.

Gathr-supported file formats for Microsoft Exchange data sources are CSV, JSON, TEXT, Parquet and ORC.

For CSV file format, select its corresponding delimiter.

Header Included #

Enable this option to read the first row as a header if your Microsoft Exchange sample data file is in CSV format.

Upload #

Please upload the sample file as per the file format selected above.

Fetch From Source #

If Fetch From Source method is selected to design the application, then the data source connection details will be used to get sample data.

Continue to configure the data source.

Connection Name #

Connections are the service identifiers. A connection name can be selected from the list if you have created and saved connection details for Microsoft Exchange earlier. Or create one as explained in the topic - Microsoft Exchange Connection →

Use the Test Connection option to ensure that the connection with the Microsoft Exchange channel is established successfully.

A success message states that the connection is available. In case of any error in test connection, edit the connection to resolve the issue before proceeding further.

Entity #

Tables in Microsoft Exchange are statically defined to model Microsoft Exchange entities.

If you selected the Fetch From Source method to design the application, the Entities will list as per the configured connection. Select the entity to be read from Microsoft Exchange.

If you selected the Upload Data File method to design the application, the exact name of the entity should be provided to read the data from Microsoft Exchange.

If you selected the Fetch From Source method to design the application, the Fields would list as per the Entity chosen in the previous configuration parameter. Select the fields or provide a custom query to read the desired records from Microsoft Exchange.

Fields #

The conditions to fetch source data from a Microsoft Exchange table can be specified using this option.

Select Fields: Select the column(s) of the entity that should be read.

Custom Query: Provide an SQL query specifying the read conditions for the source data.

Example: SELECT "Id" FROM Companies

If you selected the Upload Data File method to design the application, provide a custom query to fetch records from the Microsoft Exchange entity specified in the previous configuration.

Query #

The conditions to fetch source data from a Microsoft Exchange table can be specified using this option.

Provide an SQL query specifying the read conditions for the source data.

Example: SELECT "Id" FROM Companies

Read Options #

This section contains additional read options.

Include Content #

A boolean indicating if additional content should be retrieved, such as the Body field of an Inbox email.

Retrieving all content for a large number of items can be expensive.

This property cannot be used with the Folders table, or the Calendar child views.

Always Request Table Dependencies #

Control whether you want to always retrieve Table Dependencies (Foreign Keys).

Setting this to TRUE might slow down queries and increase amount of calls made.

Body Type #

The Body Type element identifies how the body text is formatted in the response.

The possible options are:

Best: The response will return the richest available content of body text. The default is set to Best.

HTML: The response will return an item body as HTML.

Text: The response will return an item body as plain text.

Group ID #

Specify this Group ID in order to access the OneNote documents for this group.

Impersonation Type #

The type of identifier to use with impersonation while sending requests to the Exchange site.

The pseudo-column of the same name can be used in the SQL query in order to more dynamically impersonate users.

Possible values for Impersonation Type are:

Impersonation User #

The user to impersonate while sending requests to the Exchange site.

The pseudo column of the same name can be used in the SQL query in order to more dynamically impersonate users.

Partitioning #

This section contains partitioning configurations.

Enable Partitioning #

This enables parallel reading of the data from the entity.

Partitioning is disabled by default.

If enabled, an additional option will appear to configure the partitioning conditions.

Column #

The selected column will be used to partition the data.

Max Rows per Partition: Enter the maximum number of rows to be read in a single request.

Example: 10,000

It implies that a maximum number of 10,000 rows can be read in one partition.

Advanced Configuration #

This section contains advanced configurations parameters.

Fetch Size #

The fetch size determines the number of rows to be fetched per round trip. The default value is 1000.

Add Configuration: Additional properties can be added using this option as key-value pairs.

Schema #

Check the populated schema details. For more details, see Schema Preview →