Support > Repository > CSV/Excel input/output > Upload update (repeating items and repeating containers)
ja | en

Describe the points for handling repetitive items and repeating containers in upload update.

You can update the data of "Repeat item" in the file acquired by the download function and upload update.It becomes a file as shown in Fig. 1.

Figure 1 Repeat item (when included in one file)

add to

Increased subscript (index) partAdd column (column)To do.
By specifying a minus value for the subscript, "before" can be expressed.(Example: "Telephone number [-1]")

Delete

Leave the value of the column (column) you want to delete blank, and update the upload.The data is deleted.

Add a line describing the value corresponding to the primary key and specify the number in the <Count> column.I will explain it using the example in Figure 2.

Fig.2 Repeat item (independent file)

Insert at the beginning

To insert at the beginning of a repeating item, specify -1 in the <Count> column.

Customer ID <Count> phone number
1000 -1 03-0000-0009

Add to the end

To add to the end of a repeating item, specifying 3 in the <Count> column adds the third repeating item.

Customer ID <Count> phone number
1000 3 03-0000-0010

Delete

Leave the value corresponding to the primary key blank.
In this example, spaces are specified in the phone number column.

Customer ID <Count> phone number
1000 1

Insert multiple lines at the beginning

Prepare multiple pieces of data with "-1" specified in the <Count> column.It is registered in the order of description.

Add multiple lines to the tail

Prepare more than one data with empty character in the <Count> column.It is registered in the order of description.

Handling files excluding Count column

When uploading a file not including the <Count> column, add data to the end of the repeating item.

You can change the data of "Repeat container item" in the file acquired by the download function and upload update.It becomes a file as shown in Fig. 3.

Figure 3 Repeating Container Item (When Included in One File)

Below, we explain from the place where the file of the table below was obtained by the download function.

The "id" column is the primary key item.

Table. Downloaded CSV file

id
1000

sign up

By uploading a file with added columns, you can register new containers repeatedly.

Table. Register two new repeating containers

id History [1]/history ID History [1]/Contents History [2]/history ID History [2]/Contents
1000 1 aaa 2 bbb

The order of the repeating containers is specified by the subscript of the column ("[1]", "[2]" in the above example).

add to

By uploading the file with the column added, the third repeating container will be added.

Table. Add the third repeating container

id History [1]/history ID History [1]/Contents History [2]/history ID History [2]/Contents History [3]/history ID History [3]/Contents
1000 1 aaa 2 bbb 2 (*) ccc
The value of the container ID of the added repeating container ("2" in (* in the above example)) is updated (in order)Re-setIt will be.In other words, this value can be any value (if it is an integer).

The order of the repeated containers is specified by the subscript of the column ("[1]", "[2]", "[3]" in the above example).

When the container ID is blank

If the container ID is blank, no additional processing is done.

Table. Incorrect specification method (repeating container not added)

id History [1]/history ID History [1]/Contents History [2]/history ID History [2]/Contents History [3]/history ID History [3]/Contents
1000 1 aaa 2 bbb ccc

Insert

The first iteration container is inserted by adding a column in which "-1" is appended to the subscript. The data of existing repeating containers will be shifted one by one.

In the file, it is located in the right column, but in the database after the upload update, the container with subscript "-1" is "inserted at the beginning".

Insert the first repeating container

id History [1]/history ID History [1]/Contents History [2]/history ID History [2]/Contents History [-1]/history ID History [-1]/Contents
1000 1 aaa 2 bbb 2 ccc

Delete

You can delete repeating containers by leaving the container ID value blank.
By uploading the data shown in the table below, the first repeating container will be deleted.

Remove the first repeating container

id History [1]/history ID History [1]/Contents History [2]/history ID History [2]/Contents
1000 aaa 2 bbb

update

Container ID excludedUploading the file will update it with the specified value.

Table. Update existing data

id History [1]/Contents History [2]/Contents History [3]/ContentsClerical error
1000 ddd eee fff

In this example, the value of the first repeating container content is updated to ddd and the value of the second repeating container content is updated to eee.

The third repeating container is not added and is ignored.This is because the container ID is not specified.

Repetitive containers can be treated as independent files.It becomes a file as shown in Figure 4.

Figure 4 Repeating Container Item (Independent File)

Insert

We will respond by adding a line containing the primary key and the container ID.You can also insert data by appropriately specifying the container ID.

When inserting at the beginning of the repeating container, specify "-1" in the negotiation history/history ID (container ID) column.

Customer ID Opportunity History/History ID Opportunity History/Opportunity Date Business talk history/business talk contents
1000 -1 2014/06/01 About extension of function.

You can specify more than one data whose container ID is "-1".It is registered in the order of description.

Customer ID Opportunity History/History ID Opportunity History/Opportunity Date Business talk history/business talk contents
1000 -1 2014/05/01 About extension of function.
1000 -1 2014/05/10 For details on function expansion.

add to

To add to the end of the repeating container, specify 3 in the case history/history ID (container ID) column to add the third repeating container.

Customer ID Opportunity History/History ID Opportunity History/Opportunity Date Business talk history/business talk contents
1000 3 2014/06/01 For details on function expansion.

Insert multiple lines at the beginning

Prepare multiple data with "-1" specified in the container ID column.It is registered in the order of description.

Add multiple lines to the tail

Prepare more than one data with empty character in the container ID column.It is registered in the order of description.

A file not including a container ID column

If you upload a file that does not contain a container ID column, add data to the end of the container.

Deleting repeating containers

In this method, it is not possible to delete repeating containers.

Item type

This function does not work when the referring destination of the reference linked type item is repeated and check box.

About output of detailed information

When dealing with an iteration item and an independent file of a repeating container, processing information is output to the line where the primary key appeared last in "processing result file" "error result file".In the previous line, the processing state becomes NONE and no error message is output.

I will explain this in detail.
In the example below, in the case of the 1st data in the negotiation history/negotiation day itemCharacters that can not be recognized as datesSpecify.This will result in an error.

Customer ID Opportunity History/History ID Opportunity History/Opportunity Date Business talk history/business talk contents
1000 1 Aa Greeting person in charge
1000 2 2014/06/01 For details on function expansion.

The processing result file at this time is as follows. Finally, an error message is displayed on the line where the 1000th primary key is specified.

<Success> <Process> <Message> Customer ID Opportunity History/History ID Opportunity History/Opportunity Date Business talk history/business talk contents
Success None 1000 1 Aa Greeting person in charge
Error Update Characters that can not be recognized as dates are included in the items of business day. 1000 2 2014/06/01 For details on function expansion.

Handling of the Status column

Repeating items, when dealing with independent files of repeating containers, if you specify the <Status> column, thatDesignation of the line where the primary key appeared last is valid.

I will explain this in detail.
In the example below, two lines are prepared for the 1000 primary key.At this time, "u" in the second line (update of data of primary key 1000) takes precedence."D" in the first line (deletion of the data of the primary key 1000) isIgnored.

<Status> Customer ID Opportunity History/History ID Opportunity History/Opportunity Date Business talk history/business talk contents
d Ignored 1000 1 2014/04/01 Greeting person in charge
u Effectiveness 1000 2 2014/06/01 For details on function expansion.