Data Import with Simple Forms

This manual is in pilot operation.

Data can be imported (loaded) into the ledger from a comma-separated values file (CSV file) using Simple Forms. Here are some key points about the import process:

  • Before importing data, data in input-capable cells on the screen (created by the form) will be cleared. Therefore, if there is an error in the import data, correcting the data and importing again will completely clear the previously imported data.

  • Not only amounts/numbers but also string values, boolean values, and enumeration values can be imported.

  • It is possible to specify how the signs of imported amounts/numbers are applied (debit+, credit+, according to account attribute).

  • Each key field of the input data (in CSV format) must correspond to one of the dimensions used by the target ledger (It’s okay if there are dimensions used by the target ledger that are not mapped to any key fields).

  • Code conversion is possible during import. Translation tables can be set up as many as needed. Furthermore, the content of each table can be made common across all participants or set up separately for each participant. When describing pairs of pre-conversion/post-conversion codes in the translation table, wildcards (? and *) can be used to reduce the number of entries.

Moreover, with Full-featured Forms, more advanced code conversions, such as combining multiple key fields of input data for conversion, are possible.

Format of Importable Files

Please refer to the document "Format of Importable Files (Simple Version)".

Mechanism of the Import Process

In the import process, the data is cleared before being loaded. In other words, the overall import process is as follows:

  1. Clear the values in input-capable cells on the destination screen.

  2. Load data from the source file and reflect it on the screen data.

Although the data displayed on the screen is changed in step 2 above, these changes are not saved in the database. To save, like with regular data changes, it is necessary to press the Save button.

If the import target file contains multiple data rows with exactly the same combination of key field values, the data values of these rows will be summed up during the import. If a translation table is applied to the key fields, the matching determination mentioned here will be performed on the post-conversion key field values.

Import Process Log

The course of the import process is output to a file as a process log. The file name is automatically assigned. The process log includes the pre-conversion and post-conversion values of all fields, amounts, and messages indicating the content of exception handling described later.

For more details, please refer to the document "Import Process Log".

Exception Handling

There are intended exceptions and unintended exceptions (errors). In either case, data is not written to the cells.

(1) Intended Exceptions

If the #IGNORE keyword is set in the destination code field of the translation table, data matching that line will be skipped. Also refer to Translation Table Description.

(2) Unintended Exceptions (Error Handling)

These include code conversion errors, values of fields with labels matching those of dimensions in the target ledger being inappropriate as member labels, and data outside the import range being included (not skipped).

Among the two types of exceptions mentioned above, "intended exceptions" take precedence. That is, lines targeted by intended exceptions, even if they meet the conditions for unintended exceptions such as code conversion errors, will not result in an error.

In both cases, the import process log will display a message and a code indicating the severity of the exception (#SEVERITY). In case (1), the value of #SEVERITY will be INFO, and in case (2), it will be WARNING or ERROR depending on the severity.