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
Page "Scheduled Import"
Field
|
Value
|
Import Name
|
Give the import a unique value, for example:
9002 File Storage Incident CSV Import
|
Destination Component
|
obj.com.bmssolutions.COMPONENT.bms_9999999_100
|
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: bms_9999999_49
- 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: bms_9999999_40
- Only tick the Field: Required Field
|
2
|
Refers to: Date Loaded field.
- Import Field: 2
- Destination Field: bms_9999999_44
|
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.
Therefore it will be necessary to identify:
- the Relationship between the File Storage and the Incident Component:
- Navigate to the Incident Form.
- Go to Advanced Filter. This will open the Filter Designer tab,
- Click in the "Select a Filter Field", This will open the field picker window
- For the Related Field
- Select the [Incident Number] field and click on View this will give you the Field ID for the Incident Number. In this example it would be:
bms_9999999_1873
- For the Destination Field
- Navigate to the File Storage relationship and expand it (click on the '+')
- Find the Incident as source of File Storage relationship and select it
- Click on the View button on the Tool bar of the Field Picker Window,
- This will show the details of the selected relationship. The Destination ID will be the Relationship ID (note the Destination ID setting is case sensitive). In this example it would be:
bms_FK_9999999_8337_ID
As a result, the correct entry in the Related Field Mappings would be.
Import Field
|
Settings
|
3
|
Refers to: Incident Number
- Import Field:
3 - Related Field:
bms_9999999_1873 - Destination Field:
bms_FK_9999999_8337_ID - 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
|
2021-11-01
|
3
|
D
|
INC-0000201
|
Example CSV entries:
A
|
B
|
C
|
D
|
Incident Details_001.doc
|
C:\e360_Imports\9002 File Storage Incident CSV Import\Files\IncidentDetails_001.doc
|
2021-11-01
|
INC-0000201
|
Incident Details_002.doc
|
C:\e360_Imports\9002 File Storage Incident CSV Import\Files\IncidentDetails_002.doc
|
2021-11-01
|
INC-0000201
|
|