The Native Directory import source files are CSV files.
The CSV file format is a tabular data format that contains fields separated by commas and enclosed in double quotation marks. Lifecycle Management supports only Excel-compliant CSV files. The CSV files that Excel outputs differ from the standard CSV files:
Leading and trailing white space is significant.
Back slashes are not special characters and do not escape anything.
Quotes inside quoted strings are escaped with double quotes rather than back slashes.
Excel converts data before putting it in CSV format.
Conversions that Excel performs on CSV files:
Tabs are converted to single spaces.
New lines are always represented as the UNIX new line ("\n").
Numbers of greater than 12 digits are represented in truncated scientific notation form.
A separate CSV file is available for the following entities:
Users
Groups
Roles
Provisioning info
Delegated lists
Each section within a CSV file is identified by two mandatory lines: entity and header. The entity line is identified by a predefined entity name preceded by the # character. The header line follows the entity line. The header line is a comma-separated list of predefined attributes for the entity.
The order of attributes in the header line is insignificant. However, the data lines, which follow the header line, must present data in the order in which the header line presents attributes. If data is not to be specified, use a comma to indicate that a value is not to be set. The entity line, header line, and data lines provide the information required for processing.
Boundaries applied to create, update, and delete operations on CSV files:
Users, groups, and roles are processed one data line at a time.
Group members are processed with multiple data lines under one header and one parent group.
Role members are processed with multiple data lines under one header and one parent role.
User provisioning is processed with multiple data lines under one header and one group or user.
Error handling is based on the process boundaries. One error is counted for each failure in a process boundary.
See the sections below for sample CSV files and attribute information: