Google Drive Connector > Mappings and mapping tasks with Google Drive > Google Drive sources in mappings and mapping tasks

Google Drive sources in mappings and mapping tasks

To read data from Google Drive, configure a Google Drive object as the Source transformation in a mapping or mapping task.
Specify the name and description of the Google Drive source. Configure the source, query options, and advanced properties for the source object.
The following table describes the source properties that you can configure for a Google Drive source:
Name of the active Google Drive source connection.
Source Type
Type of the Google Drive source objects available.
You can read data from a single Google Drive source object. You cannot read data from multiple objects or parameterize the object.
Name of the Google Drive source object based on the source type selected. Data Integration supports About, Changes_GetStartPageToken, Changes_List, Comments_List, Comments_Get, Replies_List, Replies_Get, Files_List, Files_Get, Files_GetAll, Files_Export, Files_ExportAll, Permissions_List, Permissions_Get, Revisions_List, Revisions_Get, SharedDrives_FilesList, Teamdrives_Get, and Teamdrives_List objects for Google Drive sources.
Configure a simple filter or an advanced filter to remove rows at the source. You can improve efficiency by filtering early in the data flow.
A simple filter includes a field name, operator, and value. Use an advanced filter to define a more complex filter condition, which can include multiple conditions using the AND or OR logical operators.
You can set the tracing level in the advanced properties session to determine the amount of details that logs contain.
The following table describes the tracing levels that you can configure:
The Secure Agent logs initialization information, error messages, and notification of rejected data.
The Secure Agent logs initialization and status information, errors encountered, and skipped rows due to transformation row errors. Summarizes session results, but not at the level of individual rows.
Verbose Initialization
In addition to normal tracing, the Secure Agent logs additional initialization details, names of index and data files used, and detailed transformation statistics.
Verbose Data
In addition to verbose initialization tracing, the Secure Agent logs each row that passes into the mapping. Also notes where the Secure Agent truncates string data to fit the precision of a column and provides detailed transformation statistics.
When you configure the tracing level to verbose data, the Secure Agent writes row data for all rows in a block when it processes a transformation.