Intended Application
For transaction importing in which a single file will contain transactions from only one location, of one transaction type and a retail value or point amount is included in the file. Records can contain transaction custom field data.
Notes
- If custom field data is for a "list" type custom field, a semi-colon must be used to separate the items.
- If an invalid parameter for a "dropdown" custom field is imported, any existing value for this field will be removed.
- For checkbox value types; 1, Y, YES = True (Checked) || 0, NO, N = FALSE (Unchecked).
- Any delimiter, except for a semi-colon and [tab], can be used to separate columns. The delimiter used is then specified at the time of file import.
- Header record is expected. The first record will not be treated as data.
- If custom field data is supplied, the appropriate custom field external reference must be referenced in the header, in the appropriate column position(s).
- Negative values will result in processing errors.
File Structure
|
DATA COLUMN |
DATA TYPE | DATA REQUIRED? | FORMATTING | NOTES |
|---|---|---|---|---|
|
Date/Time |
Yes |
MM/DD/YYYY HH:MM:SS |
24-hour clock | |
|
Alphanumeric(20) |
Yes |
|
||
| Retail Value | Decimal | Yes | 0.00 | |
| Point Amount | Decimal | Yes | 0.00 | |
| Transaction Custom Field(s) | Varies | No |
* - Denotes that the data column helps comprise the transaction unique key for this import file specification.
Sample File
In the sample below, 'MachineNum' and 'Floor' are transaction custom fields.
1: 2: 3: 4: |
DateTime|AccountId|Retail|Point|MachineNum|Floor 10/10/2010 13:14:19|1001|0.00|50.00|41321|1 10/10/2010 13:15:49|1003|19.44|50.00|41322|2 10/10/2010 13:49:50|1004|32.00|75.00|41325|3 |
