Skip to content

Import CSV File — Reference

Reference · Advanced · Server Connect

Read a server CSV file into a collection of records.

Read a server CSV file into a collection of records.

  • A Server Connect action and a disposable server file or known test collection.

Read a server CSV file into a collection of records.

Setting Meaning
NameNames the imported collection for later validation or transformations.
PathThe application-relative server CSV filename. Upload a browser-selected file first if it is not already on the server.
Import FieldsWithout a header, these are field names in column order and must match the number of columns. With a header, the header supplies names and this list checks required field presence; it does not project away other columns.
Contains HeaderUses the first CSV row as field names when enabled. Default off.
DelimiterThe separator, default comma; the literal \t setting is recognized as a tab. It must match the file.
OutputIncludes the imported records in the action response when enabled. Default off; avoid exposing private source columns unintentionally.

Use a test file with header id,name and two matching data rows. Enable Contains Header and require id and name in Import Fields. Inspect the resulting records. Test a missing header field and a row with too few columns to verify rejection.

Imported cells are text values; this is not automatic typed database import. Validate and convert them before writes. Duplicate or inconsistent headers, blank rows and embedded quotes/newlines deserve a test against the actual file producer. Use Filter Columns when you want to keep only selected fields.

Keep file parsing, data validation, database writes and file downloads explicit. A successful import/export step alone does not perform the rest of that workflow.

You can prepare the required file/data shape, configure the operation and inspect its returned file or records.