Importable File Formats (Full-featured)
This manual is in pilot operation.
|
File and Row Formats
Files to be imported must be in CSV format (comma-separated). However, if the import target file contains rows at the beginning that should not be imported, you can specify the number of such rows in "Number of Header Rows to Skip" in the Import Specification to skip them.
Each row other than those skipped contains several fields, one or more of which are Value Fields, that is, fields that hold the values to be imported. Multiple Value Fields can be defined.
The number of fields and the meaning of each field depend on the design. Specifically, the "Data source fields" defined in the Import Specification correspond to the fields in order. However, if no Value Field is defined in the Import Specification, an implicit Value Field is added at the end of the defined Data source fields.
Either LF (line feed) or CR (carriage return) can be used as line break characters. If LF and CR appear consecutively (LF + CR or CR + LF), they are treated together as a single line break.
Field values must be separated by half-width commas (,). Whitespace before or after commas is ignored. Values may be enclosed in double quotation marks. If a value contains a comma, the entire value must be enclosed in double quotation marks. Line break characters within a string enclosed in double quotation marks are not treated as row delimiters in the CSV file. In addition, if a field value string contains two consecutive double quotation marks, they are replaced with a single double quotation mark when read [1].
Blank lines in the import file are skipped.
Relationship Between Key Fields and Dimensions
A field whose Field Label matches the label of any dimension used in the destination ledger is called a Key Field. If the Key Field is a Source Field, its pre-translation value is obtained from the row data of the import file. If the Key Field is a Calculated Field, its pre-translation value is calculated by a calculation expression. In either case, after code translation, the translated value is mapped to a Dimension Member Label. Translation is performed using Translation Tables. The specifications for calculation and code translation also depend on the design and are specified by the form designer in the Import Specification.
Multiple rows in the CSV file may correspond to the same combination of members as a result of calculating and translating Key Field values. In this case, if the data type of the corresponding ledger cell is numeric (Flow or Balance), the cell value is cleared at the start of processing, and then the values from the multiple rows are added sequentially. If the data type is non-numeric, the value from the last row is written.
Key Fields and Value Fields are not mutually exclusive. A single field may be both a Key Field and a Value Field, although such a situation is expected to be rare.
Value Field Formats
The value of a Value Field may be an amount or number, logical value, enumerated value, or string value. However, it must match the Data Type of the destination ledger cell.
Numeric Formats
Numeric data may include plus signs (+), minus signs (-), commas (,) used as thousands separators and decimal points (.).
-
A plus or minus sign must be placed either before or after the number. If no sign is specified, the value is treated as positive.
-
When commas are used, the entire numeric value must be enclosed in double quotation marks.
-
The number of decimal places must be no more than four. Values with more than four decimal places cannot be read correctly.
The sign handling for numeric data can be selected as one of the following: "Debit as Plus", "Credit as Plus", or "Follow Account Attributes". This is specified by "Sign type" in the Import Specification.
When importing data by Change Accounts, set the signs for increase and decrease items as follows according to the "Sign type" in the Import Specification.
-
If "Sign type" is set to "Debit as Plus", debit increases are treated as positive and credit increases as negative.
-
If "Sign type" is set to "Credit as Plus", debit increases are treated as negative and credit increases as positive.
-
If "Sign type" is set to "Follow Account Attributes", the setting follows the "Debit/Credit Type" of the Account. Specifically:
-
For debit accounts, if the Change Account "Sign" is set to "Balance or Increase", debit increases are treated as positive. If the Change Account "Sign" is set to "Decrease", debit increases are treated as negative.
-
For credit accounts, the opposite applies.
-
Logical Value Formats
To import logical value data, specify either TRUE or FALSE in the Value Field. Uppercase and lowercase are not distinguished.
Enumerated Value Formats
To import enumerated value data, specify the value label in the Value Field. Uppercase and lowercase are not distinguished.
String Value Formats
To import string values, specify the string in the Value Field. If the string contains commas, be sure to enclose the entire string in double quotation marks. If the string value contains double quotation marks, replace each double quotation mark with two consecutive double quotation marks so that they are not confused with the double quotation marks used to enclose the entire value.
Encoding
The Encoding applied to the import file can be specified by the user during operation, as described in Changing Encoding During Operation, and does not depend on the form design. When importing string data that contains non-ASCII characters such as Japanese characters, it is important to specify the encoding correctly. The following three encodings can be used when importing from [Browser].
-
UTF-8
-
UTF-8 with BOM (fusion_place >= 14.1)
-
Shift JIS
When importing using the Requester, the encoding can be specified in the XML declaration at the beginning of the Request XML.
