This article describes the actions you should take when the bulk adding or updating of records fails.
In this article, you can find error messages and how to resolve them, as well as the actions you should take when you encounter other problems (e.g., when an empty record is added).

If an error message appears
If an empty record is added
If the text of a "Rich text" field is not displayed in multiple lines

The way to check the details of an error message differs depending on which file import method was selected when your file was imported.
For information on the action to be taken for each error message, refer to the following section.
Error messages and solutions

Any rows of data that could not be imported from the file can be downloaded in a CSV file that also contains the details of any errors that occurred. This CSV file can be downloaded on the "Imported Files" screen.
After checking the error details in the CSV file, make the necessary corrections to your file.
If the CSV file contains garbled text, refer to the following section.
If the text in your CSV file is garbled

If the bulk addition or updating of records fails, the error message "Failed to import the file." is displayed on the "View" screen.
Click Imported Files to display the "Imported Files" screen.

Edit your file for import referencing the error message displayed on the "Imported Files" screen and save the file.
To retry the file import using the edited file, click Retry Upload. On the "Import from File" screen displayed, upload the edited file.
For details on how to access the "Imported Files" screen and what kind of information it provides, refer to the following page.
Checking the Status of File Import

The following sections explain the solutions for each error.

GAIA_IL16: The value of field "***" at row number *** of the file is invalid. Please confirm the field conditions such as "Required field" or "Prohibit duplicate values", and modify the value of the file. If the field type is a "Drop-down" or a "Radio Button", the value may not match the options included in the field settings.

• If the Required field checkbox is selected in the field settings:
  Check the file and make sure a value is specified in the place indicated by the error message.

• If the Prohibit duplicate values checkbox is selected in the field settings:
  Check the file and make sure the value specified in the error message is not used in any other records.
  Also, note that you cannot import a value of more than 64 characters into a field for which the Prohibit duplicate values checkbox has been selected. Check that the number of characters used for the value is not more than 65.

• If the field type is "Radio button" or "Drop-down":
  A value that is not provided as the field's selectable options may be specified in the file.
  Check that the values specified for the field are those that are provided as the field's selectable options.

• If the field type is "Text" or "Number":
  If the maximum or minimum value for the number of characters or numbers is specified in the field settings, any value outside of the specified range cannot be imported.
  Also, note that you cannot import a value of more than 64 characters into a field that has the Prohibit duplicate values checkbox selected in its settings.
  Check the file and see if a value specified in the position indicated by the error message is within the specified range.

• If the field type is "Link":
  It is considered that the URL or e-mail address specified in the position indicated by the error message is not in the correct format.

  • If Type is set to URL in the "Link" field's settings, make sure that the URL begins with "http://" or "https://".
  • If Type is set to E-mail address in the "Link" field's settings, make sure that the e-mail address is in the correct format. (For example, make sure that the "@" symbol is entered as a half-width character.)

  For details on the formatting for each field type, refer to Supported Formats for Adding/Updating Records.

• If your file for import contains values that have a large number of digits:
  The file value indicated by the error message may be larger than the number set for Total Number of Digits in Misc Settings.
  Check the value set for Total Number of Digits on the "Misc Settings" screen in App Settings.
  Reference: Setting the Significant Digits of Numbers and the Rounding Method

GAIA_IL17: The format of field "***" at row number *** of the file is invalid. In Kintone, the supported formats for importing vary for each field type. Check the value of field "***" at row number *** in the file.

The file may have a malformed value in the field indicated by the error message.
Example:

• The file contains string values that are supposed to be imported to a Number field.
• The file contains malformed date values that cannot be recognized as a date.

Correct the data so that it is in the appropriate format for each field.
For information on the supported formats for each field type, refer to the page below.
Supported Formats for Adding/Updating Records

GAIA_IL19: Failed to lookup with the value of field "***" at row number *** of the file. The corresponding record cannot be found in the datasource app.

The value was imported as a Key for the Lookup field, but it does not exist in the datasource app.
You need to add the value indicated by the error message to the app.

GAIA_IL48: Category "***" specified at row number *** of the file does not exist in the App. Open the "App settings" and check that the value exists in the "Categories" settings.

The file contains a value that is not provided as selectable options in the Categories, as indicated by the error message.
Make sure that the file contains one of the selectable options as a value in the column associated with the Categories.

GAIA_II02: Row number *** of the file contains multiple table data. Ensure that only data for one table is included in one row of the file.

In your file for import, do not specify values of multiple tables in one row.

Example of data in the file for import:

GAIA_II03 (or GAIA_II04): This App contains tables. To import data into tables of Apps, the imported file must contain a flag (indicated by the * symbol) in the first column of each new record. If you do not want to import data from the file into tables of Apps, do not specify columns which indicate fields in the table.

• When importing data into a table:
  Check that the first column of your file for import is specified in accordance with the format suitable for importing data into tables. Specifically, check the following points:

  • Check that the first column name is "New Record Flag".
  • Check that an asterisk (*) is specified in the first column of the rows where data of each record begins and that other cells in the column are left blank.
    (In the case of GAIA_II04 error) Check that an asterisk (*) is specified in the first column of the row where data of the first record begins.

  Example of data in the file for import:
  Data specified in rows starting from the row with an asterisk (*) until the row above the one with the next asterisk (*) is recognized as the data of a single record when you add or update records via file import.
  If you import a file in the example above, data in the second row to third row, fourth row to fifth row, and sixth row to eighth row is each recognized as a single record.
  Preparing a File for Adding/Updating Records with Tables

• If you do not want to import data into tables:
  Take one of the following actions so that data will not be imported into fields in the tables.

  • Delete table data in your file for import by deleting columns for the tables.
  • Exclude fields in the table from the scope of file import when you import your file.
    To exclude fields in the table from the scope of file import, select (None) for all these fields in the Column in File column.

GAIA_II08: The file contains no value on line number *** at the column that is associated with "***" field. When you associate Created by/Updated by fields with any of the columns in "Column in File", data for Created by/Updated by fields is required in the records that you are trying to import. Select "(None)" from "Column in File" or check that the specified column is correct. In some cases, you may need to correct the file.

If you specify "Column in File" for the Created by/Updated by fields when importing records from a file, data for the specified columns needs to be included in the file.
Check if the file contains values in the column indicated by the error message or the specified columns are correct.

If you don't need to specify the Created by/Updated by fields when importing records from a file, select "(None)" from the Column in File. In that case, data for the Created by/Updated by fields will be set to the user who performed the Import from file action.

GAIA_II09: The file contains a value other than a login name or an invalid user on line number *** at the column that is associated with "***" field (The user may not exist or have been suspended/deleted. In some cases, you may not be able to view the user). Make sure that the login name is entered correctly or contact your Kintone Users & System Administrator.

The file may contain the following values in the place indicated by the error message:

• A value that is not a login name
• Login name of an inactive/deleted user or the user who does not exist
• Login name of the user who is not using Kintone
• Login name of the user in the department for which you don’t have view permission
• (If the destination app of the file import belongs to a guest space) Login name of a guest user who is not the member of the guest space

Make sure the file contains only one login name of a valid user in the columns associated with the Created /Updated by fields.

If you don't need to specify the Created by/Updated by fields when importing records from a file, select "(None)" from the Column in File. In that case, data for the Created by/Updated by fields will be set to the user who performed the Import from file action.

GAIA_II10: The file contains a line break on line number *** at the column that is associated with "***" field. Remove the line break and specify only one user login name.

The column in the file indicated by the error message might have a line break.
The file should contain only one user login name, and do not contain any line breaks in the columns associated with the Created by/Updated by fields.

If you don't need to specify the Created by/Updated by fields when importing records from a file, select "(None)" from the Column in File. In that case, data for the Created by/Updated by fields will be set to the user who performed the Import from file action.

GAIA_II12: The file contains no value on line number *** at the column that is associated with "***" field. When you associate Created datetime/Updated datetime fields with any of the columns in "Column in File", data for Created datetime/Updated datetime fields is required in the records that you are trying to import. Select "(None)" from "Column in File" or check that the specified column is correct. In some cases, you may need to correct the file.

If you specify "Column in File" for the Created datetime/Updated datetime fields when importing records from a file, data for the specified columns needs to be included in the file.
Check if the file contains values in the column indicated by the error message or the specified columns are correct.

If you don't need to specify the Created datetime/Updated datetime fields when importing records from a file, select "(None)" from the Column in File. In that case, data for the Created datetime/Updated datetime for the imported records will be set to the date and time when the file was imported.

GAIA_II13: The file contains a future date on line number *** at the column that is associated with "***" field. You need to specify a past date.

You cannot specify a future date and time for Created datetime/Updated datetime when importing records from a file.
Check the file to make sure that the columns associated with Created time/Updated Datetime fields contains the date and time is earlier than that of the import from file action.

If you don't need to specify the Created datetime/Updated datetime fields when importing records from a file, select "(None)" from the Column in File. In that case, data for the Created datetime/Updated datetime for the imported records will be set to the date and time when the file was imported.

GAIA_LM10: Failed to import the value into the Lookup field, "***". The field cannot lookup data because there is more than one corresponding record in the datasource app. Select "(None)" for the field in the "Column in File" section when you import the file. To lookup data using the value specified in the "***" field mapped column, manually enter the value into the "***" field on the record.

If any values you are trying to import into the "Lookup" field have duplicate values in the field's datasource app (i.e., the app where the data you want to retrieve is registered), they cannot be imported from the file.

In this case, register the relevant values one at a time on the "New Record" or "Edit Record" screen.

GAIA_RE10: The value in the Key to Bulk Update field in record number *** is duplicated in another record.

Check your file for import and make sure that there are no duplicate values for the field specified as the Key to Bulk Update.

To update fields in a table, select "Column in File" for all the fields in the table. You cannot update some tables; for example, a table which contains "Attachment" field. For more details, refer to the Help.

If you have selected the Key to Bulk Update checkbox, you need to specify corresponding file columns for all of the fields in the table that are displayed under Field in App. You must also specify corresponding file columns for fields whose data has not been modified in the file.

If the error still appears even though you have specified corresponding file columns for all the fields in the table, there is a possibility that the table contains any of the following fields:

• "Attachment" fields
• "Lookup" fields (If Prohibit duplicate values is disabled for the field specified as the Key Field)

If a table contains either of the fields above, you will not be able to import data into any of the fields in the table when updating existing records via file import.
In such a case, select (None) for all the fields in the table to exclude them from the scope of file import.

Failed to start importing the file, because the app settings were updated while you configured the file import. Possible causes are: "fields were added into the table" or "settings of the fields in the import file were changed". Please confirm the updated settings and change the import data, then try to import the file again.

Field settings are changed or new fields are added while the "Import from File" screen is displayed.
Apply the changes to the file for import, and then try importing the file again.

In some cases, you may find garbled text in the CSV file downloaded on the "Imported Files" screen when you double-click it and open it in Excel.
In this case, open the file using Excel's feature for importing data from the data source.
For details, refer to the following page.
Microsoft Help: Opening CSV UTF-8 files correctly in Excel

If a CSV file for import has a row that contains only delimiters which you have specified when you import the file (comma, semicolon, space, or tab), the row will be imported as an empty record.
Open the CSV file using a text editor or other equivalent software and delete the row that contains only delimiters.

To add the data of rich text fields including line breaks, the file need to contain the data written in HTML format.
In the file to import, insert '<br>' at the position where you want to have a line break.