|
Example: Importing into the File Storage Component (Attachments)
Following is a step by step instruction of how to set up an Import of File Attachments.
To create an Import from scratch, you need to:
- From the menu, select Designer
Imports Data Import NEW
OR
- From the menu, select Designer
Imports Data Import Import Wizard
Page "Import Details"
Field
|
Value
|
Import Name
|
Give the import a unique value, for example:
9002 File Storage Incident CSV Import
|
Destination Component
|
File
|
Type of Import
|
CSV File
|
Rollup Table(s)
|
Do not rebuild
|
Page "CSV File"
Field
|
Value
|
Directory Location
|
This will be the local path on your tomcat server, where the CSV file will reside, for example:
C:\e360_Imports\9002 File Storage Incident CSV Import
|
Allow Double Byte Characters
|
Leave unchecked (Answer = No)
|
First row is a header row
|
Check (Answer = Yes)
|
Page "Mappings"
Field Mappings
The Field Mappings are used to import the columns of the CSV file into the correct Column of the target Component.
The first two entries are mandatory, the third entry is optional.
Import Field
|
Settings
|
0
|
Refers to: File Name
- Import Field: 0
- Destination Field: File Name
- Only tick the Fields: Key, Required Field
|
1
|
Refers to: Relationship to the File Field, and will require Path and File Name.
- Import Field: 1
- Destination Field: Attached File
- Only tick the Field: Required Field
|
2
|
Refers to: File Description field.
- Import Field: 2
- Destination Field: File Description
|
3
|
Refers to: Date Loaded field.
- Import Field: 3
- Destination Field: Date Loaded
|
Related Field Mappings
This is necessary to link any Attachments to a Parent Record. For the following Example, the Assumption is that the File Attachments are linked to Incident Records.
As a result, the correct entry in the Related Field Mappings would be.
Import Field
|
Settings
|
4
|
Refers to: Incident Number
- Import Field: 4
- Matching Field: Incident Number
- Destination Relationship: Incident as source of File Storage
- Append: False
|
Preparing the CSV file
For the Import to work correctly, the CSV file will need to contain the following information at a minimum:
Import Field
|
Maps to Column in the CSV File
|
Example
|
0
|
A
|
IncidentDetails_001.doc
|
1
|
B
|
C:\e360_Imports\9002 File Storage Incident CSV Import\Files\IncidentDetails_001.doc
NOTE: This field does require the full path, including the name of the file itself.
|
2
|
C
|
File Description
|
3
|
D
|
2021-11-01
|
4
|
E
|
INC-0000201
|
Example CSV entries:
A
|
B
|
C
|
D
|
E
|
Incident Details_001.doc
|
C:\e360_Imports\9002 File Storage Incident CSV Import\Files\IncidentDetails_001.doc
|
Incident Image 001
|
2021-11-01
|
INC-0000201
|
Incident Details_002.doc
|
C:\e360_Imports\9002 File Storage Incident CSV Import\Files\IncidentDetails_002.doc
|
Incident Image 002
|
2021-11-01
|
INC-0000201
|
|