To import transactions from a file you can either:
Supported file formats are:
Please note that a licensed base unit is required to import data in Quicken Interchange Format.
Tip: Hold down the control key while dropping a file onto the Account List to prevent any auto-assignment of saved settings. Refer to the section on Saving Definitions for more information.
When a file is first dropped on the Account List it is parsed to determine the format of the data contained. The initial import view will be presented using these results.
Map Transaction Fields to Import Columns.
There are a number of steps that need to be taken before the file data can actually be imported:
Should it be necessary, you can select-click on the Import File Format button to open the Import File Format Dialogue. From here you can:
Click Set to confirm your changes. The import file data is re-evaluated and the import view updated accordingly.
You can not revise the import file format after adding a calculation or changing the format of a column.
The format of an import column is important. A transaction field can only be populated with data of the correct format. Import columns can be formatted as either:
If the auto-parse fails to correctly identify a column's format it can be set manually from the Column Definition Dialogue. There are a number of reasons why a column's initial format could be wrong, these include:
Depending on the source of the import data, it may be necessary to provide additional data in order to 'fill in the gaps'. This is achieved by adding additional columns, in the form of calculations, to the import view.
These calculated columns can be either:
Calculated columns are maintained via the Column Definition Dialogue.
Before a Transaction can be built, !EnBank needs to know which columns are to be used to populate the transaction fields. This process is known as Import Field Mapping and is performed via the Import Field Mapping Dialogue.
When you open the Import Field Mapping Dialogue you may find that some, or all, of the transaction fields have been 'auto-mapped' to import columns. Auto-mapping takes place when a column, of the correct type, is found to have the same name as the field in the Transaction Audit View.
All fields must be mapped to columns before the import data can be verified.
Before data can be imported, it must first be verified. The verification process checks the import data for errors and ensures that the resulting transactions are valid.
Select-click on the Verify Import Data button to start the process.
The error message "Import data contains errors which must be resolved before you can post" is issued if there are any problems with the data. Click Detail to see the Import Audit Log which will identify all of the issues that need to be resolved.
A successful verification will enable the Import button. Any subsequent changes will require a reverification of the import before it can be imported.
Once verified, the data can be imported by select-clicking on the Import button.
After the import is complete, the view remains open. However, the Import button is disabled to prevent accidental importing of the same data. Run the verification again to reactivate the Import button.
Once verified, an import definition can be saved for future use.
Enter a valid RISC OS file name into the Name field and click Save.
Please note that import definitions can only be saved with a licensed base unit.
Settings can be automatically assigned to an import file. When a file is dropped onto the Account List, its file name is used to search any import definitions for a match. The best matching definition, if any, is then used to build the initial Import View.
The file specification of the file used to create the definition and against which import file specifications are matched. For a new definition this will be the current import file.
Click New to reset the 'auto match' file to the current import file name and start a new definition using the current definition as a template.
To have a definition automatically assigned to an import file you must select one, or more, of the match options: Name, Directory or Full Specification.
Use this definition when the import file specification matches the definition file specification.
Full Specification matches are used in preference to Directory and Name matches.
Use this definition when the directory element of the import file specification matches the definition.
Directory matches are used in preference to Name matches.
Use this definition when the name element of the import file specification matches the definition.
Saved definitions can used manually in the following ways:
Launching an import from the Account List menu opens both the definition and the import file specified. The file specified by the definition must exist.
To open the dialogue for a column:
There are two types of column:
Applies to both Field and Script column types.
The name of the column.
Used by Field Mapping to map Columns to Fields and by the JavaScript column object.
For Scripts, this is also the name of the script, and therefore, the context within the Import run-time of the JavaScript environment.
The data format of the column. Valid formats are:
A column must be of the correct format to be mapped to a Transaction field. For example, only Date columns are available for mapping to the Transaction Date field.
The Places field is used to set the number of decimal places for Numbers.
Import data is rounded to the specified number of places before been used to populate a Transaction.
The number field in the import file is formatted as a monetary value.
This option only affects how the numeric string in the import file is converted to a real number. It does not alter how the field is used by !EnBank.
Both numbers and monetary values are expected to be formatted according to the current RISC OS Territory. Refer the section on choices for details of how to override the Territory Manager.
Only available for Script columns.
The Script, or Constant, for the calculated column.
If the first character of the script is an equals sign, '=', then the column is considered to be a constant rather than a script. For example '= "text"' would set the value of the column to 'Text'.
To enter a script, either:
Scripts are validated when you click on Set. If the script is found to contain errors you will get an error and the dialogue box will remain open. Refer to the section on JavaScript for more information.
Select-click on Edit to edit the script with your editor of choice.
To use the edit function you will require a text editor that supports OLE, !Zap for example. There is also a module available called OLESupport that simulates OLE for non OLE compliant editors such as !Edit. This module should be in !System.310.Modules, if not then use www.drobe.co.uk to do a 'Downloadable File' search for 'OLESupport'.
The Import Field Mapping Dialogue is used to map import Columns to the Fields of the Transaction.
Auto-mapping: each time the dialogue is opened, an attempt is made to map unassigned fields to their default columns.
The pop-up menu to the left of each Field contains the names of columns suitable for mapping to that Field. If you do not see a column you were expecting, check the column's format.
Some columns can also be mapped to a Default Behaviour rather than a specific column.
Map both the From Account and the To Account fields to the same column if you want !EnBank to assign the account based on the sign of the value mapped to the Transaction.
Transaction Type, Format: Text, Default column: 'Type'.
This field must contain a valid Transaction Type.
Default Behaviour: Set to Credit, Debit or Transfer depending on the account allocation.
From Account, Format: Text, Default column: 'From'.
A valid Account ID, or '<None>', must be specified.
If Mapped to the same column as the From Account then the specified account will be used if the assigned value column is positive.
To Account, Format: Text, Default column: 'To'.
A valid Account ID, or '<None>', must be specified.
The Transaction must be assigned at least one actual Account ID.
If Mapped to the same column as the From Account then the specified account will be used if the assigned value column is positive.
Transaction Date, Format: Date, Default column: 'Date'.
Date the transaction occurred.
From Account Statement Number, Format: Number, Default column: 'FS'.
The number, or zero if none, of the statement this transaction appears on.
A Transaction with a none zero statement number will be imported as a Verified transaction.
Default Behaviour: Set to zero.
To Account Statement Number, Format: Number, Default column: 'TS'.
The number, or zero if none, of the statement this transaction appears on.
A Transaction with a none zero statement number will be imported as a Verified transaction.
Default Behaviour: Set to zero.
Transaction Number, Format: Text, Default column: 'No.'.
A reference for the transaction.
Note: Although this field is optional, it must still be mapped to a column.
Default Behaviour: No number assigned.
Descriptive Text, Format: Text, Default column: 'Description'.
Description for the Transaction.
The Transaction Scratch-pad can not be populated via an import.
Analysis Group, Format: Text, Default column: 'Group'.
A valid ID for an Analysis Group, or the text '<None>'.
Default Behaviour: Set to '<None>'.
Analysis Class, Format: Text, Default column: 'Class'.
A valid ID for an Analysis Class, or the text '<None>'.
Default Behaviour: Set to '<None>'.
Transaction Value, Format: Number, Default column: 'Local'.
The value of the Transaction, in Local currency.
Currency Code, Format: Text, Default column: 'Cur.'.
A valid Currency Code representing the currency the value is specified in.
Default Behaviour: Set to Base Currency.
Exchange Rate Type, Format: Text, Default column: 'Rate'.
A valid Exchange Rate Type, as defined via the Currency Maintenance program, !EnCurr.
If the Transaction is not in Account Currency, then, an exchange rate of the type specified here must exist for the specified currency and date.
Default Behaviour: Set to default Exchange Rate Type as specified in Choices.