When you import users or groups into Adobe Connect Enterprise Manager, you may see errors if you don't use the correct format. In order to perform this task without errors, you need the correct column headers in a CSV file. However, you may not be able to determine which columns are required.

Reason

The documentation that contains the column headers is not accessible easily from within the Adobe Connect Enterprise Manager, nor is there a quick reference that displays the column headers needed.

Solution

Create a CSV file using the required column headers for Users or Groups, as instructed below.

To import Users:

• Select "Create new users and add them to a group" to import the new users into a group that exists in Connect.
• Select "Add existing users to a group" to add existing users in Connect to an existing group.

Additional Information

Tips for using CSV files:

• Because of browser limitations, Adobe recommends that you create several smaller CSV files instead of one large CSV file when you are adding a large number of users.
• The file should not contain empty lines. If the CSV file contains empty lines, then the import operation fails with this error message in red "The import operation is complete and all valid entries have been committed to the system. Invalid lines were found in the CSV import entries." The user(s) which caused the failure will be listed, allowing you to correct the problem with the user(s); then you can re-import the CSV file.
• Names that contain a comma must be in quotation marks. For example, the name John Doe, Jr., must appear in the CSV file as œJohn Doe, Jr. for the file to import correctly.
• If you want to specify a custom field, then the header format in the CSV file is x<fieldid> (for example, x45704960). You can obtain the field ID from the XML API calls custom-fields or acl-field-list, or you can click the Custom User field in Enterprise Manager and check the ID in the URL.
• The user information in the CSV file needs to take login and password policies into consideration. For example, if login is set as email, the CSV file should have the login and email columns set the same. Or, if there are password policies (certain length, format, special characters, etc.) these policies should also be applied in the CSV file. If policies are not followed, the import operation fails with this error message in red "The import operation is complete and all valid entries have been committed to the system. Invalid lines were found in the CSV import entries." The user(s( which caused the failure will be listed, allowing you to correct the problem with the user(s); you can then re-import the CSV file.