Quickbase ETL Source

Gathr provides Quickbase channel to read Apps data from Quickbase.

Schema Type #

See the topic Provide Schema for ETL Source → to know how schema details can be provided for data sources.

After providing schema type details, the next step is to configure the data source.

Data Source Configuration #

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 MongoDB earlier. Or create one as explained in the topic - Quickbase Source Connection →

Table Name: All the tables will be listed from the application authenticated in the connection. Select a table to read the data.

Fields: All the fields along with field IDs will be listed as per the table selected. Select the fields that are required to be read.

Where Clause: Option to exclusively fetch schema results or read data from source as per the filter condition or query provided.

Sort By: The records that are fetched from the table will be sorted with reference to the field selected. The sorting preference will be from top to last in case of multiple entries.

Group By: The records that are fetched from the table will be grouped with reference to the field selected. The grouping preference will be from top to last in case of multiple entries.

Additional Query Options: Optionally specify the query options.

Example:

{
“skip”:0,  
“top”:1,  
“compareWithAppLocalTime”:false  
} 

Records Per Partition: The number of records that should be fetched in parallel from the specified table.

Example: For reading 1000 records, if the partition value is given as 100, then 100 records in 10 partitions will be fetched in parallel.

Add configuration: Additional properties can be added using Add Configuration link.

Detect Schema #

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

Incremental Read #

Optionally, you can enable incremental read. For more details, see Quickbase Incremental Configuration →

Pre Action #

To understand how to provide SQL queries or Stored Procedures that will be executed during pipeline run, see Pre-Actions →)

Notes #

Optionally, enter notes in the Notes → tab and save the configuration.