Using the Import tool, you can import many database fields from a CSV file.
| Field name | Field type | Description |
|---|---|---|
|
|
String | Strings in time and date format. |
|
|
String | Strings in time and date format. |
|
|
Unsigned integer | Number of inactive days before credential or cardholder expires. |
|
|
Unsigned integer | Number of days after first use before a credential or cardholder expires. |
|
|
String | Credential badge template. |
|
|
Unsigned integer or string | Credential card format. You can use one of the following values:
To specify a custom card format, you must spell it exactly as you created it. If no card format is specified in a CSV line, the default format specified on the import settings page is used. |
|
|
Standard card format | You can specify a field in a specific card format, including custom card formats. |
|
|
Standard card format | Field of an old credential to replace. These “(previous value)” choices appear only if you selected Replace as Credential operation. |
|
|
As defined by the custom field | Cardholder custom field. |
|
|
String | Name of the cardholder group the cardholder should belong to. If the cardholder group does not exist, it is created in the same partition as the cardholder. |
|
|
Boolean | Valid inputs (in English, not case sensitive):
|
|
|
As defined by the custom field | Credential custom field. |
|
|
String | Use this field
to enter credential data as a string of decimal values, with individual fields
separated by either the / or | character.For
example, for a credential that uses the Standard 26-bit card format, the
string must include the facility code, followed by the separator character,
followed by the card number. The string For custom card formats, arrange the data according to the custom card format definition. When you specify this field, the individual fields such as Facility code and Card number are ignored. |
|
|
String | Use this field to enter the credential
data as a hexadecimal string, followed by the | character, followed
by the credential bit length in decimal. The hexadecimal string matches how the
credential data is stored in the database.For example,
When you specify this field, the individual fields such as Facility code and Card number are ignored. |
|
|
String | Cardholder entity description. |
|
|
String | Cardholder email address. |
|
|
String | Cardholder first name. This field is part of the default cardholder key. |
|
|
String | Cardholder last name. This field is part of the default cardholder key. |
|
|
String | License plate number. Use the cardholder’s license plate number as a credential. Use this method when a Sharp camera triggers a vehicle access barrier. |
|
|
String | Cardholder's mobile phone number. |
|
|
String | Credential entity name. If no name is specified, the default value “Imported credential” or “Unassigned imported credential” is used. |
|
|
String | Name of the partition the cardholder should belong to. If the partition does not exist, it is created. If it is not specified, the cardholder is put in the system partition. |
|
|
String | Name of the partition the credential should belong to. If the partition does not exist, it is created. If it is not specified, the credential is put in the system partition. |
|
|
String | Path to a cardholder picture file (bmp, jpg, gif, or png). The path must reference a file located on the local machine or on the network. |
|
|
String | Credential corresponding to a PIN. The maximum length is 15 digits. |
|
|
Boolean | Cardholder status. The following values are accepted (in English, not case sensitive):
|
|
|
String | Credential status. The following values are accepted (in English, not case
sensitive):
|