Quickbase
Quickbase ETL connector for data replication
Features | Details |
Release Status | Released |
Source API Version | 2.0 |
Table Selection | Yes |
Column Selection | Yes |
Edit Integration | Yes |
Replication Type Selection | No |
Authentication Parameters | Quickbase Api token
Quickbase App id
Quickbase Realm Host name |
Replication Type | Full Replication
Key based replication |
Replication Key | NA
lastRunDate |
Suggested Replication Frequency | 24 hrs |
Tables/APIs Supported | |
Reports | Relationships |
Fields | Tables |
UsageFields | App |
- 1.Signin to Daton
- 2.Select Quickbase from Integrations page
- 3.Provide Integration Name Replication Frequency and History. Integration name would be used in creating tables for the integration and cannot be changed later
- 4.Provide your Quickbase api token, Quickbase app id and Quickbase realm Host name to authorize Daton to periodically extract data Quickbase.
- 5.Post successful authentication you will be prompted to choose from the list of available tables
- 6.Then select all required fields for each table
- 7.Submit the integration
- 1.Integrations would be in Pending state initially and will be moved to Active state as soon as the first job loads data successfully on to the configured warehouse
- 2.Users would be able to edit/pause/re-activate/delete integration anytime
- 3.Users can view job status and process logs from the integration details page by clicking on the integration name from the active list
Reports
Purpose: Get the schema (properties) of all reports for a table. If the user running the API is an application administrator, the API will also return all personal reports with owner's user id.
Replication: Key-Based Replication
Replication Key: lastRunDate
Fields
Name | Target Datatype |
id | STRING |
name | STRING |
type | STRING |
description | STRING |
query | RECORD |
properties | RECORD |
Relationships
Purpose: Get a list of all relationships, and their definitions, for a specific table. Details are provided for both the parent and child sides of relationships within a given application. Limited details are returned for cross-application relationships.
Replication: Full Replication
Replication Key: NA
Fields
Name | Target Datatype |
metadata | RECORD |
relationships | RECORD |
Fields
Purpose: Gets the properties for all fields in a specific table. The properties for each field are the same as in Get field.
Replication: Full Replication
Replication Key: NA
Fields
Name | Target Datatype |
id | STRING |
label | STRING |
mode | STRING |
fieldsType | STRING |
noWrap | BOOLEAN |
bold | BOOLEAN |
required | BOOLEAN |
appearsByDefault | BOOLEAN |
findEnabled | BOOLEAN |
unique | BOOLEAN |
doesDataCopy | BOOLEAN |
fieldHelp | BOOLEAN |
audited | BOOLEAN |
properties | RECORD |
Tables
Purpose: Gets a list of all the tables that exist in a specific application. The properties for each table are the same as what is returned in Get table.
Replication: Full Replication
Replication Key: NA
Fields
Name | Target Datatype |
id | STRING |
name | STRING |
description | STRING |
alias | STRING |
nextFieldId | NUMERIC |
defaultSortFieldId | NUMERIC |
nextRecordId | NUMERIC |
keyFieldID | STRING |
singleRecordName | STRING |
pluralRecordNmame | STRING |
defautSortOrder | STRING |
created | TIMESTAMP |
updated | TIMESTAMP |
sizeLimit | STRING |
spaceRemaining | STRING |
spaceUsed | STRING |
UsageFields
Purpose: Get all the field usage statistics for a table. This is a summary of the information that can be found in the usage table of field properties.
Replication: Full Replication
Replication Key: NA
Fields
Name | Target Datatype |
field | RECORD |
usage | RECORD |
App
Purpose: Returns the main properties of an application, including application variables.
Replication: Full Replication
Replication Key: NA
Fields
Name | Target Datatype |
created | TIMESTAMP |
dateFormat | STRING |
description | STRING |
hasEveryoneOnTheInternet | BOOLEAN |
id | STRING |
name | STRING |
timeZone | STRING |
updated | TIMESTAMP |
Last modified 2yr ago