Import Data file format
When importing data using the Import Data tab, the imported data must be in CSV format.
Click here to view a spreadsheet with sample CSV files for a series of records. The files should be imported sequentially according to their number.
Note The CSV format must use UTF-8 encoding to retain special characters such as language accents. For more information, see How to create a CSV file with UTF-8 encoding from an Excel file.
- The file must include the fields marked as Required in the Administration > Configuration > Studio > Fields tab for the selected record type, with the exception of fields that are auto-populated by the system (such as the Create time field).
- You may select any additional fields to include in the file as necessary for each record.
- The imported records must adhere to any restrictions defined in the workflow and the business rules for that record.
- For more information about the fields of a specific record type, refer to the section of the documentation for that record type.
The files should be imported in a logical order, based on the dependencies between the record types. If a record file includes a field that references a related record, the file for the related record type should be imported first. For example, the device record file may include the OwnedByPerson field, which includes data contained in the contact record file. If the contact record file is not imported first, the device import may fail.
Note When selecting the field and attribute used to reference a related record, it is recommended to use an attribute with a unique value. For example, OwnedByPerson.Upn could be used to reference the unique identifier of the owner.
For more information on the specific fields for each of the records in this example, see:
- Users and contacts
- How to create an actual service record
- How to create a service definition record
- How to create a category
- How to create a device record