56
API_ImportFromCSV
•
Overview
•
Request parameters
•
Response values
•
Sample XML Request
•
Sample XML Request to Add New Records
•
Sample XML Response (Added New Records)
•
Sample Response (Updated Existing Records)
Overview
Use API_ImportFromCSV to add or update several records. You invoke this call on a table-level dbid. You
can add AND update in the same API_ImportFromCSV request. (For an Add, leave the Record ID empty.)
The clist parameter is optional when adding new records to a table. When updating existing records, the clist
parameter must contain the field ID for the key field (usually 3 for the Record ID#). The CSV file you're
importing must also include a column that contains the value of the key field for each record that will be
updated.
Request parameters
PARAMETER
VALUE
REQUIRED?
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
s
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
Yes, if you are
updating records, or
you want the columns
in the CSV file to map
to certain fields in the
table.
Page 185
