Import reference
For how import works, see Importing data. For step-by-step instructions, see How to import data.
Supported file formats: .xlsx, .xls, .csv. The maximum file size is 10 MB. When this is violated, the system shows the message “Unsupported file format. Allowed extensions: …” or “File is too large. Maximum size: …”.
Asset import fields
Section titled “Asset import fields”The fields are available in the “System field” column on the mapping step. Required fields must be mapped, otherwise you cannot move on to the run.
| System field | Required |
|---|---|
| Inventory number | Yes |
| Asset type | Yes |
| Name | No |
| Manufacturer | No |
| Model | No |
| Serial number | No |
| Quantity | No |
| Price | No |
| Residual value | No |
| Commissioning date | No |
| Date of completion of operation | No |
| Date of purchase | No |
| Warranty expiry date | No |
| Location | No |
| Employee ID | No |
| Employee last name | No |
| Employee first name | No |
| Employee patronymic | No |
| Comment | No |
The inventory number serves as the key for identifying duplicate assets.
Employee import fields
Section titled “Employee import fields”| System field | Required |
|---|---|
| Employee ID | Yes |
| Last Name | Yes |
| First Name | Yes |
| Middle Name | No |
| Phone | No |
| No | |
| Position | No |
| Department | Yes |
The employee ID serves as the key for identifying duplicate employees.
Duplicate-handling strategies
Section titled “Duplicate-handling strategies”The strategy is chosen on the Parameters step before the run.
| Strategy | What it does |
|---|---|
| Skip duplicates | A row whose key already exists in the system is not loaded and is counted as skipped. |
| Update existing | The existing record is updated with the data from the file. For assets the option is called “Update existing assets”, for employees “Update existing employees”. |
Duplicates are identified by inventory number (assets) or by employee ID (employees).
Result categories
Section titled “Result categories”After the run, four counters are shown on the Result step.
| Category | Meaning |
|---|---|
| Imported | New records created. |
| Updated | Existing records updated (only with the “Update existing” strategy). |
| Skipped | Rows skipped — for example, duplicates with the “Skip duplicates” strategy or rows without a required key. |
| Errors | Rows that could not be processed. |
Skip and error reasons
Section titled “Skip and error reasons”If there are skipped rows or errors, an Import protocol is shown below the counters with the columns Row, Type, Field, and Reason. The type is either “Skipped” or “Error”.
Known skip reasons:
| Record type | Reason in the protocol |
|---|---|
| Assets | Duplicate: a record with this inventory number already exists |
| Assets | Asset type is not specified |
| Employees | Duplicate: an employee with this ID already exists |
| Employees | Employee ID is not specified |
For rows with the “Error” type, the “Reason” column shows the error text returned while processing the row; the field is not specified in this case.