3.5.2 Importing custom table records

This section describes the [Import] tab of the Datamodel application.
On the [Import] tab, you can import records in bulk from a CSV file containing records of a custom table, for example when introducing Ops I, and create or update records.
In this section, jobs for importing records are referred to as import jobs. To use the [Import] tab, you must be assigned the Primitive role “resource_importer”.
In addition, to import records, you must register an Import YAML file in advance. For details about the Import YAML file, see “Import”.

(1) “Import job list” window

Clicking the [Import] tab displays the “Import job list” window.
In the “Import job list” window, you can check the import status and, if an error occurs, identify the row in the CSV file that caused the error.
Records of registered custom tables can be viewed from the [Custom Data Model] tab. For details, see “Custom data models”.

The “Import job list” window consists of the [Import] button, the [Delete] button, and the “Import job list”. The details are as follows.

(Table) Components of the “Import job list” window

(2) Upload File window

Clicking the [Import] button in the “Import job list” window displays the Upload File window.
In the Upload File window, you can import a custom table by specifying an Import Definition and uploading a file.

The Upload File window consists of the [Start import] button, the [Cancel] button, the Import Definition, and the file upload area. The details are as follows.

(Table) Components of the Upload File window

Component	Description
[Start import] button	Clicking this button imports the records in the CSV file uploaded in the file upload area in the format selected in the Import Definition. This button is disabled if no format is selected in the Import Definition or if no file has been uploaded to the file upload area.
[Cancel] button	Clicking this button displays the "Import job list" window without executing the import.
Import Definition	Selects an import definition. Clicking the icon displays the [Import Definition] dialog box. After selecting an import definition and clicking the [OK] button, the dialog box closes and the selected value is entered. The import definition displayed must be defined in advance in an Import YAML file. For the "name" or "label" label in the Import YAML file, set a name that clearly indicates the destination table for the import. For details, see "Importing records from custom tables".
File upload area	Upload a CSV file containing records of the custom table to be imported. Clicking the "select" link in "Drop or select a file to add" displays the file operation dialog box. To upload a CSV file, select it in the file operation dialog box or drop it into the dotted area. You cannot upload multiple CSV files simultaneously. You can upload a file that meets the following conditions: The file size must be 100 MB or less. The character encoding must be UTF-8 (without BOM). If you select a CSV file exceeding 100 MB, an error message will be displayed and the import will not be performed.

In the CSV file, enter data items on the first line, separated by commas (,). From the second line onward, enter the values to be imported, separated by commas (,) and in the same order as on the first line.
When specifying multiple values for a single data item, separate the values with semicolons (;).

For importing records into a custom table, the behavior of the import varies depending on the conditions at the time of import.
If the CSV file is mapped to the custom table, the records in the CSV file are applied to the custom table.
If the CSV file is not mapped to the custom table, the records to be applied vary depending on the following conditions:

• Whether the records are newly created or updated
• Whether the columns are default Ops I columns or user-created columns

The combinations of the above conditions and the corresponding behavior are shown in the following table.

(Table) Behavior at the time of import

Tips
When you import records obtained from an Ops I custom table into another Ops I, it is recommended to set "id" as the unique identifier (coalesce: true).
In other cases, it is recommended to set an appropriate record in the CSV file as the unique identifier and not to set "id" as the target in columnMappings. If "id" is not set as the target, a value that is unique within Ops I is automatically assigned to "id".

When records of a custom table are imported, the data format in the CSV file corresponding to the column types in the Datamodel YAML file is as follows. For details about the column types in the Datamodel YAML file, see “(Table) Column types”.

(Table) CSV file data formats corresponding to column types in the Datamodel YAML file

Datamodel YAML file column type	CSV file data format
integer	Integer
numeric	Number with decimal point
varchar	String The default maximum length of a string is 40 characters. You can change the maximum length of a string by specifying "varchar(number of characters)". The maximum allowable string length is 10,485,760 characters.
text	String
timestamp	Format: YYYY-MM-DDThh:mm:ss±hh:mm Example: 2026-01-05T14:30:00+09:00
date	One of the following formats: YYYY-MM-DD YYYY-MM-DDThh:mm:ss±hh:mm If entered in YYYY-MM-DDThh:mm:ss±hh:mm format, it is converted to YYYY-MM-DD format. Example: 2026-01-05
time	Format: hh:mm:ss Example: 14:30:00
boolean	true or false
enum	Format defined in the Datamodel YAML file
inet	Format: CIDR (IPv4) Example: 192.168.1.1
decimal	Number with decimal point
uuid	Format: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX "X" represents an alphanumeric character (a-f, 0-9). Example: 550e8400-e29b-41d4-a716-446655440000 Tips Use a uuid compliant with RFC9562 (versions 1-8).

<Specification examples>
The specification examples for a Datamodel YAML file, an Import YAML file, and a CSV file are as follows.

■Datamodel YAML file

■ Import YAML file

■ CSV file