API_ImportFromCSV

records_csv

An aggregate containing the actual records you are importing.

<records_csv>
   <![CDATA[
      your, record, values, go, here
      and, hopefully, here, as, well
   ]]>
</records_csv>


For field format, usage, and any validation for fields of particular types, see API_AddRecord.

yes

clist

A period-delimited list of field IDs that indicates how the columns in the CSV file will map to fields in the table when the import happens. To prevent a column in the CSV file from being imported, enter a 0 in the field ID list.

This means that the first field ID in the list maps to the first column in the CSV file, the second field ID maps to the second column in the CSV file, and so forth.

In the following example, the CSV file contains 4 columns. Quickbase will not import either the first or the third columns. The second column will map to field ID 7, and the fourth column will map to field ID 6.

<clist>0.7.0.6</clist>

Yes, if you are updating records, or you want the columns in the CSV file to map to certain fields in the table.

clist_output

Specifies which fields should be returned in addition to the record ID and updated ID. Specify a period-delimited clist string, for example:

<clist_output>0.7.0.6</clist_output>


no

decimalPercent

Set this parameter to 1 so that decimal values like 0.50 will be interpreted to mean 50%.

no

skipfirst

Set this parameter to 1 to prevent Quickbase from importing the first row of data in a CSV file. You must specify this parameter if the first row of your CSV file contains column names.

Omit this property if you don't want to prevent the first row to be imported.

no

ticket

A valid authentication ticket.

The authentication ticket is returned via the API_Authenticate call.

yes, one of:

• ticket
• username/password
• user token

usertoken

The user token is an alternative means of authentication, used for API access. User tokens cannot be used to access the Quickbase UI.

yes, one of:

• ticket
• username/password
• user token

apptoken

A valid application token.

yes, if the application requires application tokens

udata

A string value that you want returned. It will not be handled by Quickbase but it will be returned in the response.

no

msInUTC

Allows you to specify that Quickbase should interpret all date/time stamps passed in as milliseconds using Coordinated Universal Time (UTC) rather than using the local application time.

Set this parameter to 1 if you want to use Coordinated Universal Time. See usage example.

no

mergeFieldId

With this parameter, the import uses the field specified as the key, instead of the key field for the table.

• The merge field must be a unique field, and the specified merge field must contain unique values.

• Values for the table key and/or record ID field will be ignored from input to prevent data corruption.

• If the specified merge field uses a formula, and a record cannot be found by its value, a new record will be added if the resulting formula value is a valid value for the field.

• Record ID or other table key field can be used as the specified merge field.

• The clist parameter is required if this parameter is used.

To specify the field, use the field ID, for example:

<mergeFieldId>10</mergeFieldId>

For more details, read an article about the parameter on the Quickbase Community site.

no

action

The originating request, for example, API_ImportFromCSV.

errcode

Identifies the error code, if any. (See the Error Codes appendix for a list of possible error codes.)

0 indicates that no error was encountered.

errtext

Text that explains the error code.

"No error" indicates that no error was encountered.

udata

Optional. Contains any udata value supplied in the request.

num_recs_added

The number of records added to the table

num_recs_input

The total number of records in the CSV file

num_recs_updated

The number of records in the table that were updated

rids

A list of the record IDs for all the records that were either added or updated

update_id

Attribute of each rid element that defines the update_id for the record.

Update IDs are used to detect update conflicts in subsequent operations with API_EditRecord.