Preparing the csv file, Uploading csv files, Avoiding duplicate identities and errors – Avigilon Access Control Manager - Collaboration User Manual
Page 22: Mandatory fields, Field list
Collaboration Administrator Manual
17
Preparing the CSV File
To properly upload a CSV file into the application, it is important that the data be formatted
correctly and the CSV created properly. Use the CSV upload example template on page 19 to aid
in creating an identity CSV file. The very first row of the CSV file is reserved for column headers.
Make sure that the data in the rows reflects the column names. Moving a date or name to a
different column will cause the identity CSV upload to fail.
Uploading CSV Files
To upload an identity CSV file:
1. At the Collaboration Add page, create a new collaboration with either the Identity CSV
One-Time Upload
Short form or Identity CSV One-Time Upload Long form type
selected.
2. If this is the long form, supply values to the three text fields as required.
3. Click
to save the collaboration.
4. From the upload selection box, click the
.
The Find File dialog box appears.
5. Locate the CSV file you need and select it.
The new CSV file appears on the collaboration edit page.
6. Save to start the upload process.
Avoiding Duplicate Identities and Errors
Running the identity CSV upload twice will result in identities being duplicated. Also, having an
error occur in the middle of an upload then starting over from the beginning can result in duplicate
identities. Duplicate identities can easily be deleted in the Identities section of the application. If
an error occurs, a message will appear on screen with approximate CSV line location. This will
help locate the error and start the CSV upload at the point where the last record failed.
Mandatory Fields
Not every field must have a value, but there are three mandatory fields: First name, Last Name,
and Status. If these fields do not have values, the upload will not work properly.
Field List
There are currently 19 fields that are available for uploading data:
External System ID
The ID assigned to an identity by the user. For example, the primary key of an SQL table
that the user row is being pulled form. The external ID is a string and will accept
alphanumeric characters as well as hyphens, underscores, etc.
Load Date
The date that the user ID is loaded into the table. The specific date format is mm/dd/yyyy
or 07/04/2012 for example.