« Participant Authorities   |   Importing and Exporting Participant Authorities »

Importing and Exporting Participants

Administrator
This manual is in pilot operation.

Importing Participants

Participants can be added, updated, or deleted in bulk based on the data registered in an Excel sheet. This functionality is referred to as the "Participant Import Feature."

Procedure:

Format of Importable Data

The import process involves capturing data from an Excel sheet via the clipboard. Specifically, copy the range containing the configuration details from the Excel sheet to the clipboard, and then import it into the participant editing screen. On the sheet, each item should be written in its column. The format of importable data is detailed below, but if it seems unclear, try exporting an existing participant to an Excel sheet and pasting it. The exported data can be imported as is, following the rules below.

General Rules Regarding Notation

For fields other than participant names, uppercase and lowercase letters are not distinguished.

Rules Regarding Row Order

The copy range on the Excel sheet begins with a "Header Row" followed by any number of "Detail Rows". The header row directs the meaning of each field in the detail rows. Each detail row represents the content of adding, updating, or deleting a participant. Empty rows can be placed at any position within the copy range and will simply be ignored.

Rules regarding the arrangement of header and detail rows are as follows:

  1. The first row (excluding empty rows) within the range must be a header row.

  2. After the header row, any number of "detail rows" can be placed. The arrangement of fields in these detail rows must follow the order indicated by the preceding header row.

  3. Within the range, it’s permissible for the header row to appear multiple times.

  4. Each detail row represents the content of adding or updating a participant. It’s allowable to use multiple detail rows for a single participant. In such cases, these detail rows are processed in the order they appear on the sheet.

Rules Regarding Header Row Content

The header row consists of the fields listed in the table below.

Field Name Required Number of Fields Field Position Specification (Field Symbol)

Command

✓

1

Always the first field

One of the following:

For adding/updating: ADD_OR_UPDATE_PARTICIPANT

For deletion: DELETE_PARTICIPANT

Record Type

✓

1

Always the second field

Fixed value: HDR

Label

✓

1

Optional

Fixed value: LABEL

Name

―

One for each defined " language "

Optional

Fixed value NAME: + Locale

NAME:ja

Name in Japanese
NAME:en

Name in English

Access Permission Type

―

1

Optional

Fixed value: ACCESS_PERMISSION_TYPE

Responsibility Key

―

Optional

Optional

Fixed value R: + Dimension Label.

Example: For specifying a key for the account
R:#ACCOUNT

The command ADD_OR_UPDATE_PARTICIPANT indicates that the detail rows following this header row are instructions for adding or updating participants. Similarly, the command DELETE_PARTICIPANT indicates that the detail rows following are instructions for deleting participants.

The record type “HDR” denotes that this row is a header row.

The name field is indicated by the fixed value NAME followed by the "locale", such as ja or en, connected by a colon :. Do not place spaces before or after the colon. The locale can be in uppercase.

The responsibility key field is indicated by the fixed value R: followed by the property label, connected by a colon :. Like the name field, do not place spaces around the colon. The fields always required are the command, record type, and label. Other fields may be added or omitted as necessary.

The order of fields other than the command and record type is arbitrary.

Rules Regarding Detail Row Content

In the detail rows, appropriate values are specified for each field designated in the header row. Therefore, each detail row must have the same number of fields as the immediately preceding header row. The fields in the header and detail rows are matched in the order they appear. The specified values for each field in the detail rows are as follows:

Field Name Specification (Field Value)

Command

Specify the same command as in the preceding header row

Record Type

Fixed value: DTL

This indicates that the row is a detail row.

Label

The label of the participant being added, updated, or deleted in each row.

In the case of add or update instructions, if a participant with this label exists, it will be updated according to the instructions in this detail row.
On the other hand, if the corresponding participant does not exist, the participant will first be added. Then, as in the case of an update, its contents will be set according to the instructions in this detail row.

Name

The name of the participant in each language.
(If the field symbol is NAME:ja, then the name in Japanese, NAME:en for English name, etc.)

Access Permission Type

The label of the Access Permission Type to be assigned to the target participant.

Responsibility Key

The Responsibility Key (Member Label) for the target participant for the dimension specified in the header row. If no Responsibility Key is specified for the dimension, leave it blank.

Exporting Participants

The configuration of all participants can be pasted into an Excel sheet in the format described above for import (the data is exported to the clipboard and then pasted from the clipboard into the Excel sheet). The content of this sheet can be modified and re-imported.

Procedure: