Skip to content

Import

Overview

This function imports department information to the "Department administration" screen from a CSV file. You can register current departments in bulk.

Preparations

  • Prepare the data to import as a CSV file in advance.
  • Shift-JIS or UTF-8 can be used for the character code of the CSV file.
  • Add a header (the name of each item) to the first record of the CSV file.

Items That Can Be Imported

The items that can be imported from a CSV file when creating or updating are as follows. Items marked with × are ignored even if they are included in the CSV file.

Item Create new Update
Department ID × ×
Department code 〇 × *1
Department name 〇 〇
Description 〇 〇
Comments 〇 〇 *2
Disabled *3 〇 〇
Created by × ×
Updated by × ×
Updated on × ×

*1 When updating, it is treated as the import key.
*2 In the case of JSON format, comments are updated by replacing them all. In the case of string format, they are not updated.
*3 Check "Access Restrictions with Security.json" in the limitations.

Procedure

  1. Click the "Import" button at the bottom of the "Department administration" screen.
  2. Click the "Choose File" button in the "CSV file" item and select the CSV file to import.
  3. Select the character code of the CSV file to import.
  4. Click the "Import" button.
  5. The message "xx entries have been added and xx entries updated." is displayed at the bottom of the screen.

Limitations

  1. As with importing a normal table, a header record is required.
  2. Only the items specified in the header record are registered and updated.
  3. "Department code" and "Department name" are required items. Importing a record without "Department code" or "Department name" results in an error.
  4. "Comments", "Updated by", "Created by", and "Updated on" are ignored when importing.
  5. A record with the same "Department code", not the same "Department ID", is updated as the update target. If there is no record with the same "Department code", the record is imported as a new registration.

Access Restrictions with Security.json

Security.json has a function that allows access to Pleasanter on a department basis when "AllowIpAddresses" and "IpRestrictionExcludeMembers" are set together. If you use this function to allow access on a department basis, disabling a department prevents the users who belong to the department from accessing Pleasanter.

If a user with important administrative privileges, such as a tenant manager, can no longer access Pleasanter, it may be necessary to change the IP address of the device in use or to reconfigure Security.json.

*If you do not restrict access by IP address with "AllowIpAddresses" in Security.json, you do not need to consider the above limitation.

Supported Versions

Supported Versions Body
1.4.18.0 and later Added the ability to update comments when updating records in CSV import