For you to be able to import CSV files using the Import tool, the CSV file needs to follow a certain format and include specific information for each type of entity. These files can be created from an Excel spreadsheet.
Minimum information required in CSV files
The information found in the CSV file must be coherent or it will not be accepted by the Import tool. When required information is missing, the Next button in the Bindings page is disabled. Each type of imported entity requires a minimum amount of information.
The following table describes what is required for each type of entity.
|Entity type||Minimum information required|
|Credential - Card||You have the choice of two credential keys:
If you choose a custom card format, all fields required by your card format must be bound to a column in the CSV file. Otherwise, the CSV file will be rejected.
When credential are being imported, either one of these two keys must be present. If both keys are missing values, the line will be discarded. If both keys are present, only the card data is imported.
|Credential - License plate||Enter a cardholder's license plate number. Use this method if a Sharp camera is being used to trigger a vehicle access barrier. In this case, the cardholder's vehicle license plate can be used as a credential.|
|Credential - PIN||
PIN credentials can be used with cards or as standalone credentials. Make sure that each cardholder's PIN is unique if you plan to use your readers in Card or PIN mode.
|Cardholder||The default cardholder key is the combination of the cardholder’s first and
last name. One of these two fields must be bound to a CSV column if cardholders are
to be imported.
When cardholders are being imported, all CSV lines must have a value in at least one of these two fields. If not, the line would be discarded.
|Cardholder group||Only the cardholder group name is required. Missing the cardholder group will not cause a line to be discarded.|
|Partition||Only the partition name is required. Missing the partition name will not cause a line to be discarded.|
Format of the CSV file
Below is an example file called EmployeeData.csv, containing 3 new cardholders to import. It can be created from an Excel spreadsheet by doing "save as" and selecting the .csv format".
#First name,Last name,Cardholder description,Cardholder email,Picture, Cardholder group,Cardholder status,Credential name,Facility code,Card number,Credential status Abdoulai,Koffi,Market Analyst,firstname.lastname@example.org,C:\Data\Cardholder\Pictures\ Abdoulai Koffi.png,Marketing,Yes,82968378,102,8,active Andrew,Smith,Sales Representative,email@example.com,C:\Data\Cardholder\Pictures\ Andrew Smith.png,Sales,Yes,82748590,101,12,active Audrey,Williams,Technical Writer,firstname.lastname@example.org,C:\Data\Cardholder\Pictures\ Audrey Williams.png,TechWriters,Yes,83748952,104,18,active
The first row is a comment line, listing the cardholder and credential fields that are included in the CSV file as a reference. The following three rows contain the fields that will be imported. You also can add additional custom fields if they have been created for cardholder or credentials in Security Center.
Custom field limitations
- You cannot import custom fields using the Entity data type.
- Custom fields using the Date data type must be imported with the format ‘YYYY-MM-DD’.
- The Import tool performance decreases as the number of custom fields per imported record increases.
- When you have a large number of custom fields per record, the number of records you can import at once might also be limited. For example, if your records contain 100 custom fields each, including a 25 KB image data field, you can only import 1000 records at a time.