Delimited Input Schema

The following table explains the attributes and corresponding description available in a delimited input schema:

Attribute Name Description
Name

The file record names have alphanumeric characters only. Each name is unique within the plug-in configuration.

Description (Optional) A short description for the delimited file record.
Strip Blanks

Select this check box to remove the blank spaces for each field identified for a record in a data file.

Repeating Delimiter

Specifies whether to ignore repeated delimiters. Select this check box to translate any repeated delimiters between fields as only one field separator. Clear this check box to translate repeated delimiters as empty fields.

Delimiter

Specifies the separator between fields within each line of a file for the line that is parsed. Space, Tab, and Other are the available options. If you select Other, the Delimiter Other field becomes available.

Delimiter Other

This field is available only if you select Other from the Delimiter field. Specifies the delimiter to be used. You can specify single or multiple characters as a delimiter.

To distinguish delimiter characters from actual field values, you can enclose data fields including the delimiter characters in double quotes.

For example, a John, "3301 Hillview Ave, Palo Alto CA" comma delimited record is treated as two fields because of the double quotes.

Note: Quoted field is supported with regular records only. End-of-line cannot be enclosed in double quotes.
Identifier Type

Specifies the method to identify a record. Field Value (constant field value) and Number of Fields are the available options.

When the Identifier Type field is set to Field Value, the constant attribute for one of the fields needs to be specified when defining the fields for the records. If the constant field matches but the count exceeds the expected field count, then line is parsed successfully and a warning message is displayed: The line {0} has been mapped with class {1}, extra fields of the input line has been discarded in Output XML.

For example, a input schema defines a record to contain three String fields with the first field containing a constant string "Order". A record, such as "Order,ID1234,Aug20" is accepted by parser activity. However, a record with a valid constant "Order" but contains four fields, such as "Order,ID1234,Aug20,CA" is parsed successfully but "CA" will not be a part of the output XML. The following warning message is displayed: The line [Order,ID1234,Aug20,CA] has been mapped with class [Order], extra fields of the input line has been discarded in Output XML.