## Overview This function allows you to input and output department information from the "Department Management" screen as a CSV file. You can perform initial registration of current departments in bulk and obtain department information in bulk. Shift-JIS or UTF-8 can be used for the character code of the CSV file. ## Import ### Preparation Please check the character code in advance. If the names of the table column and headers of the CSV to be imported do not match exactly, the column will be ignored, so please add a header (the name of each column ) to the first line of the CSV. ### Limitations 1. As with importing a normal table, a header record is required. 1. As with importing a normal table, only the column specified in the header record will be registered and updated. 1. "Department Code" and "Department Name" are required column . An error will occur if a record without a "Department Code" or "Department Name" is imported. 1. "[Comment](/en/manual/table-management-comments)", "Updater", "Creator", and "Updated Datetime" are ignored during import. 1. Records with the same "Department Code" but not the "Department ID" will be updated as the update target. If there is no record with the same "Department Code", it will be imported as a new registration. #### Access Restrictions with [Security.json](/en/manual/security-json) [Security.json](/en/manual/security-json) has a function that allows access to Pleasanter on a department unit by setting "AllowIpAddresses" and "IpRestrictionExcludeMembers" together. If you are using this function to enable access to a department unit, please note that deleting/disabling a department/deleting a user who belongs to it will prevent the user from accessing Pleasanter. Suppose a user with important administrative privileges such as a tenant manager can no longer access Pleasanter. In that case, it may be necessary to change the device's IP address or reconfigure [Security.json](/en/manual/security-json). *If you have not restricted access by IP address using "AllowIpAddresses" in [Security.json](/en/manual/security-json), you do not need to consider the above restrictions. ### Column that can be imported The columns that can be imported in CSV when creating or updating are as follows. Columns marked with × will be ignored even if they are listed in the CSV. |Column|Create New|Update| |:----|:----|:----| |Department ID|×|×| |Department Code|〇|× *1| |Department Name|〇|〇| |Description|〇|〇| |Comment|〇|〇| |Invalid *2|〇|〇| |Creator|×|×| |Updater|×|×| |Updated Datetime|×|×| *1 When updating, it is treated as an import key. *2 Please check "Access restrictions by [Security.json](/en/manual/security-json)" in the limitations. ### Procedure 1. Click the "[Import](/en/manual/table-record-import)" button at the bottom of the "Department Management" screen. 1. Click the "Select File" button in the CSV file field and select the CSV file to import. 1. Select the character code of the CSV file to import. 1. Click the "[Import](/en/manual/table-record-import)" button. 1. When the message "〇〇 column added and 〇〇 column updated" is displayed at the bottom of the screen, the process is complete. ## Export ### Limitations 1. When exporting from the "Department Management" screen, unlike exporting a list of tables, all data is included regardless of whether the checkbox is selected or not. ### Procedure 1. Click the "[Export](/en/manual/table-record-export)" button at the bottom of the "Department Management" screen. 1. The export dialog will be displayed. Select the format and character code. (Only "Standard" can be selected as the format. Shift-JIS or UTF-8 can be selected as the character code.) 1. The file will be downloaded.