Sometimes, Quickbase may not be able to refresh your connected data. The connection owner can usually resolve this using the information below. If you’re still having trouble, reach out to our Quickbase Technical Support team.
Find information about connected tables
View connected table details and history
To view Details about your connected table, including the connected service, connection owner, connected fields, filter, and schedule for the connected table, access the connection in table settings. You can also view a History of recent refreshes, and edit the connection filter, refresh schedule, or switch to use a different connection, if necessary.
View, test, or delete your connections
To view details about your connection and test, change, or delete connections, select the user dropdown on the global bar, then Profile. Your connections display in the My Connections area.
General errors
General errors may apply to connected tables for any data source.
Error | Explanation | How to fix the issue |
|---|---|---|
Rate limit exceeded | Connected tables can have up to one scheduled refresh per hour, and a reasonable number of manual refreshes to accommodate normal business processes. Excessive refreshes within a time period may result in a Rate limit exceeded error. | Wait before trying the manual refresh again. |
Connect to cloud services
If you're having trouble connecting or refreshing data from cloud services, you may see one of the following:
Error | Explanation | How to fix the issue |
|---|---|---|
Column does not exist | The connected table is looking for a column in the service that no longer exists or is not accessible, based on permissions granted by the connection.
| If you don't need this field, remove the field from the connected table and edit the connection filter, if it includes any unavailable fields. |
Invalid field | The column in the service may have been deleted. | If you need access to this data, sign in to the service with the same credentials and find out if the data is accessible. |
Does not recognize queried object | Access privileges in the service may have been changed or the current connection may not have access to the table or fields. | You may need to make adjustments to your account, or if the data is not accessible using the credentials you signed in with, you'll need to use a connection with different credentials. See switch connections. |
Query requires additional inputs Requires credentials Login verification failed Invalid credentials | The login to the data source isn’t working. | Verifying your credentials and/or access to the data source and then test and update your connection.
|
Table source not found | We’re having trouble accessing a table in the data source. | Try again later. |
Create a connection to Salesforce.com
If you're having trouble creating your Salesforce connection, check with your administrator to make sure Salesforce.com API access and permissions are enabled. Salesforce.com requires that your Salesforce.com account have API access enabled. Your user account must also have the API Enabled permission selected.
See Salesforce User Permissions for more information.
Connect to a table in another Quickbase app
If you're having trouble connecting to or refreshing from a table in another Quickbase app, you may see one of the following:
Error | Explanation | How to fix the issue |
|---|---|---|
No such operation SSL connection required Unknown hostname Reading the QuickBase API_Authenticate response from ... Reading the QuickBase QBIGetDBInfo response from ... We couldn't save your connection We couldn't connect to Quickbase | The Quickbase URL is incorrect. | Locate the Quickbase URL in the browser. For example, https://myco.quickbase.com. Copy and paste the correct URL into the Quickbase URL field. Don’t include the /db/ portion and what comes after it when copying and pasting into the Quickbase URL field. Be sure to use https instead of http in the Quickbase URL field. |
No such database or login operation requires a database name | The database ID is missing or incorrect. | Open the home page of the app. In the URL that displays, copy the alpha-numeric text that displays after db/. For example, bi4zjv7mq. |
Invalid application token | The application token is missing or incorrect. | Copy or create an app token for the app you want to connect to. On the app home page, click Settings, then click Manage Application Token. Copy and paste the app token into the App Token field. |
There was a problem refreshing the table The error was: Invalid input - QB error code: 2 | Possible causes include:
|
|
Connect to the Admin Console
If you are a realm admin and you do not see the Admin Console channel as an option listed in the sources when setting up a new connected table, check to make sure you have not exceeded the limit of three Admin Console connected tables per realm.
Connect to a folder containing CSV files
If you're having trouble connecting to a folder containing CSV files, you may see one of the following:
Error | Explanation | How to fix the issue |
|---|---|---|
Table replication requires non-null key values | Null key values refers to empty cells in the column used as the Refresh Key field. | Update the CSV file to include a value for this field in each record or change the Refresh Key. |
We couldn't open the fields list |
| Update the CSV file so that each field in the header row has a unique name. Save the file as a UTF8-encoded .csv. Make sure the value in the Refresh Key field is unique for each record (no duplicate entries or missing entries). |
The resource '[[connection_3226]]."Complete data export":ServiceDefinitionTable' does not exist. | The connected folder could not be found within the Quickbase Sync folder in the file storage service (Box, Dropbox, Google Drive). | Make sure the folder displays in the file storage service, inside the Quickbase Sync folder, and that it contains a valid .csv file. |
The source data includes non-unique key values, the column value(s) from the source query that correspond to the destination key column(s) must be unique. | Multiple rows in the CSV file have the same value in the Refresh Key field. | Review the structure of your CSV file and the intended use of the data to determine how best to resolve duplicates and understand which column, containing unique values, makes the best Refresh Key for your data. |
Unknown column: IndexName | An expected column name was not found in the CSV file. | Review your CSV file to determine if a column name changed. |
Error parsing .csv. A cell contains an invalid quoted string. | The CSV file does not conform to the standard, such as a value containing an un-escaped double quote. | Review your CSV file and ensure that is it a UTF-8 encoded .csv files in which:
|
The file was example.csv. The error was: Invalid character in row 00001, field 1, position 1. | The CSV file contains a character that is not a valid UTF-8 character. | Locate and remove the invalid character. The error message identifies the first invalid character that is encountered in the file. The file’s header row is considered row 1. The field (column) number is based on the order the connected fields were added to the connected table. The position is where in the field the invalid character is located. |
Note: If your automatic refresh schedule was set to manual because of a number of unsuccessful refresh attempts, review the most recent error message in the table history and resolve the problem. After you resolve the problem, you can reset the refresh schedule to automatic.
If you’re having trouble, please open a support case.