Transaction Export and Import

Transaction Export and Import

Version 2.2

OmniValue supports export and import of transactions. The export and import can be made in the native OmniValue format or in a plain text format. The text file format is suitable for data exchange with other software applications such as e.g. Microsoft Excel.

Transaction Export
Format
Transaction Import

Transaction Export

To export transactions select the Asset containing the transactions and select menu Value->Export (or right click on the Asset and select menu Export). Here, the asset IBM containing a Buy, a Dividend, and a Sell transaction is selected.

Select menu Export to export transactions.

The export can either be made in OmniValue format or in text format. If text format is used a delimiter has to be defined. The delimiter separates the fields in the text file. It can be any printable character or even a sequence of characters. The delimiter can also be a TAB, "\t", or a Line Feed, "\n". In this example a text format export using a semicolon, ";", as delimiter is specified in the dialog.

Format

After exporting the Buy, Dividend, and Sell transaction in the IBM asset the text file contains the following:

#Transaction;ID;Record Date;Payment Date;Count;Value;Fee;Note
Buy;110;12/12/2000;12/12/2000;1000.000000;63.500000;0.000000;""
Dividend;510;3/5/2001;4/8/2001;1000.000000;0.750000;0.000000;"IBM Dividend"
Sell;310;5/7/2003;5/7/2003;600.000000;78.000000;0.000000;""

The first line in the text file is the header with captions for each column. The header line starts with the number sign (#). The number sign (or hash mark) indicates that the line is a comment and that it should not be parsed by a software application reading the file.

After the first line the transactions are listed in chronological order, one transaction per line. The data fields for a transaction are separated by the delimiter specified in the dialog (here a semicolon).

Column	Data	Description
1	Name	The name of the transaction.
2	ID	ID for transaction. The transaction is identified using a OmniValue ID. A complete list of all IDs for all predefined transactions in OmniValue is given in chapter 1
3	Record Date	Record date for the transaction.
4	Payment Date	Payment date for the transaction.
5	Count	Transaction unit count.
6	Value	Transaction value.
7	Fee	Transaction fee.
8	Note	Transaction note.

Transaction Import

Import of transactions follows the same procedure as described in the chapter for transaction export. To import transactions into an Asset select menu Value->Import (or right click on the Asset and select menu Import). If the import is in text format a delimiter must be specified.

An example of a text import file is:

# Data file from external software application
# Generated on 01/13/08
Buy;110;12/12/2000;*;1000.000000;63.500000;0.000000;""
Dividend;510;3/5/2001;4/8/2001;1000.000000;0.750000;0.000000;"IBM Dividend"
*;310;*;5/7/2003;600.000000;78.000000;*;""

The format for an import file must follow the format specified above. In addition, the following rules apply for transaction import:

A field can be marked as unspecified by using the * character
The transaction name field is not used by OmniValue (since OmniValue identifies the transaction by its ID). The name field can be marked as unspecified by using a *.
The transaction ID field is mandatory. The ID must be a value specified in the list of IDs in chapter 1.
If the record date is not specified, the record date will be the same as the payment date (and vice versa).
The record date and the payment date can not both be unspecified.
If the count, value, or fee field is unspecified the import will default to 0.0 for the field.

If OmniValue fails to import a transaction a dialog will be displayed showing which line in the import that failed.