CSV Export-Import to-from Dataset to-from

Export to Dataset and Import CSV from Dataset Action

(Requires EAM) These CSV import/export actions can be used to move tabular data between programs that operate on incompatible, proprietary formats.

The CSV: Import from Dataset Action reads data from a comma-separated values (CSV) file, and populates the specified dataset with those values.

The CSV: Export to Dataset Action can be used in conjunction with Protocol: Listing to Dataset Action and Loop: Dataset (or with an existing dataset) to create a CSV file, which can then be used in other applications.

Refer to Datasets in Event Rules for information about using datasets in Event Rules.

In the Dataset drop-down in the Export CSV Action, do not specify a non-existent dataset, especially if you do not plan to dynamically create that dataset in the script via other means (such as PowerShell). If you specify a non-existent dataset, the action will fail and an error will appear in the EFT log (Export failed. Error: Dataset does not exist.)

CSV file format is not standardized; EFT allows multiple-character delimiter without any length limit. If the Treat first line of data as column headers check box is cleared, the dot notation for referencing the fields in records will be: Column0, Column1, Column2, and so on. For example, %Customer.CurrentRow.Column0%.