This deprecated node imports the contents of a delimited file using the specified set of field and record delimiters.
If the node has an input, use the FilenameExpr property to determine the names of the files to process. The list of files is constructed using the current row of the input file, and applying the specified expression.
If the node does not have an input, use the File property to determine the files to process. Both FilenameExpr and File may not be specified at the same time. You can use either absolute or relative file paths, but note that if the file path is relative, then the temporary directory of the data flow for the current run is used as the base to which the file path is relative.
When the node has an input pin, all of the files must conform to the same specification, that is, have same number of fields in the same order and format. In the situation where the files to be imported have different fields, or the fields are in a different order, one solution would be to import the files individually and then use the Cat node to combine the individual data sets.
An additional output pin can be added to the node; if there are two outputs, the second output is an error output.
When the FilenameOutputField property is specified, the node outputs an additional field. The contents of this field contain the filename from which the output record was imported. This is especially useful when the node is used to import multiple files as it allows the origin of each record to be traced back to its source file.
Properties
File
Click the folder icon and browse to the file that you want to import.
If you use this property, do not also use the FilenameExpr property.
FilenameExpr
Specify which data to use for the filename, if filenames are processed from an added input. The result of the expression specified in the FilenameExpr property must identify the input field containing the filenames. For example, if the Delimited File node is connected to the output of a Directory List node, the property would be set to FileName. Alternatively, an expression could be used to dynamically select the field containing the filenames, for example by using a Boolean run-time property:
evalIf({{^UseFileName^}}, Field_A, Field_B)
If you use this property, do not also use the File property.
FileCharacterSet
If you are not using the default US-ASCII character encoding set, select the appropriate option to ensure that your data is displayed correctly.
The default value is US-ASCII.
FieldDelimiter
Specify the field delimiter. The field delimiter is the character sequence used to separate fields in the file to be imported. For example, use \t as the field delimiter for a file with fields that are separated by tabs. If the fields are separated by commas, enter the comma character "," (enter just the character, with no quotes).
A value is required for this property.
RecordDelimiter
Specify the record delimiter. The record delimiter is the character sequence used to separate records in the file to be imported. For example, use \r\n or \n as the record delimiter for a text file in which each line contains a single record.
A value is required for this property.
FilenameOutputField
Optionally specify the name of a field to add to the output containing the input filename.
If left blank, no filename field is added to the output.
FieldNames
Optionally specify a comma-separated list of names to be used as the output field names. By default, the node assumes that the first line of the input file is the header record and its contents are used to derive the output field names.
EscapeCharacters
Optionally specify a comma-separated list of escape characters (for example, backslash \).
The default value is none.
QuoteCharacters
Optionally specify a comma separated list of quote characters.
The default value is none.
QuotedDoubleQuotes
Optionally specify how to treat data which contains quotation marks (such as "abc""def").
Microsoft Excel CSV format does not use different escape characters. Instead, it uses quoted double quotation marks to make a literal single quotation mark. The above would therefore be interpreted as abc"def
Other formats (such as shell scripts) would not interpret the quotation marks, since the double quotation marks both end the first quoted sequence and immediately start the next. The example above would therefore be interpreted as abcdef. These formats usually use different escape characters to make literal quotation marks. Choose from:
- Literal Quote - Always treats double quotation marks as literal quotes.
- Nothing - Treats double quotation marks as nothing.
- Literal Quote if no EscapeCharacters - Treats double quotation marks as literal quotes if no escape characters are specified, and nothing if escape characters are specified.
The default value is Literal Quote if no EscapeCharacters.
Inputs and outputs
Inputs: 1 optional (filenames).
Outputs: out1, 1 optional (errors).