RFC 4180 parser
Please note the following for the RFC 4180 parser.
This parser is only available for creating and managing Secure FTP sources.
For more information on the RFC4180 specification, see https://tools.ietf.org/html/rfc4180.
Note: For Secure FTP sources created before the RFC 4180 parser was available, you can follow the steps for Managing sources and edit the source to configure a new parser.
Multi-line CSV data
To import data from source files that have multi-line data and use a Secure FTP source, you must select the RFC 4180 parser in the source configuration. The Open CSV parser only supports data imports from source files that have single-line data.
Important: Multi-line data must be enclosed in double quotes, while single-line data may or may not be enclosed in double quotes.
Data record size limits
The RFC 4180 parser supports ingesting data records with up to 99 line breaks. If a data record contains more than 99 line breaks, Oracle Unity will report an error during ingestion.
Supported delimiters
When configuring a source, the only supported delimiter for the RFC 4180 parser is the comma (,).
Importing empty or null data
-
To update the Oracle Unity data model with empty or null data, learn how to Different ways to represent empty or null data in source files.
-
Review the Restrictions on empty or null data.
Managing double quotes
To manage double quotes inside a quoted string, insert another double quote before the quote inside the string: “Asd "” asd".
Configuring the RFC 4180 parser with the Oracle Unity API
Review RFC 4180 File standards for the Oracle Unity API from the Oracle Unity Developer Help Center.
Review these resources to configure sources and ingest jobs using the Oracle Unity API from the Oracle Unity Developer Help Center.