Automatically Import Data
Using saved Import Templates, an import routine can be automated as a task.
-
From within the Tasks grid view, either double-click on a selected task row, or click on the Edit The Edit Tasks dialogue window appears.
-
Select an Import Template (See also Import Templates).
-
Enter the File Name including the path to the destination folder for the file. It is possible to save a filename with a wildcard * attached, to allow for the importation of related files over a period of time.
-
You can also click ... to locate the file on your device or within your network. You can also specify an FTP site or Web Service from which data will be imported.
-
(Optional) Check if an Appending File. This will append the incoming file without replacing the previous file.
-
(Optional) Uncheck Save raw file to Document if you do not wish to save incoming raw data files. It is recommended that you uncheck Save raw file to Document option when automated imports such as Telemetry are carried out frequently. This can prevent the database from growing exponentially.
- Check your Level 1, Level 2, Level 3 to which you are importing. For a data import, if the source file includes Level 2 or Level 3 data, the Level 2 or Level 3 names will be blank.
-
After import, select which action you require from Do Nothing, Delete the File or Move the File. In order to Move the File, you must specify a Target Location where the file will be moved. Allowing for a file to be moved or deleted after importation, means that the DataSight service does not import the same files over and over. You can specify an FTP Site as your Target Location.
-
(Optional) When Move the File is selected, you can archive the imported file into sub-directories within the Target Location, based upon the import file's modification date.
-
Check Archive Files Using Last File Modification Date - (Creates sub-directories for archiving into your target location).
-
You must select one of the sub-directory hierarchy options:
-
Check Year Only - Archive your files into sub-directories by year; or
-
Check Year\Month - Archive your files into sub-directories by year, and then within each year by month; or
-
Check Year\Month\Date - Archive your files by year, month, and then within each month by date.
- (Optional) To add sub tasks, click Add Sub Tasks (See Add Sub Tasks for more details).
- (Optional) If a Calculation subtask is added in the previous step, then you can choose to Run Calculation Sub Tasks on Imported Data only.
- Set the Recurrence interval over which you wish to run the Task and its subtasks (if any).
- Click OK.
- Remember to click Save in the Quick Access Toolbar to save the entire Task set, prior to closing the Tasks grid view.
|
Note
|
When creating an import task for data from a Web Service, the full connection string must also be used on creating the import template. See also Select Your File and Web Service.
|
Level Selection Options Based on Import Template
The design of the Import Template will define which Level 1, Level 2 and Level 3 selections are made available to you in your Import Task. Three options are available as detailed below.
|
Option
|
Import Template Design
|
Task Level Selections Available
|
|
Step 2: Filter and Map Your Data
|
Step 4: Relate Your Data
|
Task Section: Details
|
|
Level 1 Name
|
Level 2 Name
|
Level 3 Name
|
Level 3 ID
|
Level 1
|
Level 2
|
Level 3
|
Level 1 Selection
|
Level 2 Selection
|
Level 3 Selection
|
|
1
|
Cannot be mapped
|
Mapped
(Must be mapped if Level 3 Name is mapped)
|
Mapped
(Must be mapped if Level 2 Name is mapped)
|
Cannot be Mapped if Level 2 Name & Level 3 Name are mapped
|
Enabled for mandatory user input
|
Disabled for user input
|
Disabled for user input
|
Pre-populated with the Level 1 that was selected from Import Template Step 4. Enabled for user input allowing user to override the Level 1 defined in the Import Template.
|
Level 2 is determined by the Imported Data. Disabled for user input.
|
Level 3 is determined by the Imported Data. Disabled for user input.
|
|
2
|
Cannot be mapped
|
Cannot be mapped if Level 3 ID is mapped
|
Cannot be mapped if Level 3 ID is mapped
|
Mapped
|
Disabled for user input
|
Disabled for user input
|
Disabled for user input
|
Disabled for user input
|
Disabled for user input
|
Level 3 is determined by the Imported Data. Disabled for user input.
|
|
3
|
Cannot be mapped
|
Is not mapped
|
Is not mapped
|
Is not mapped
|
Enabled for mandatory user input
|
Enabled for mandatory user input
|
Enabled for mandatory user input
|
Pre-populated with the Level 1 that was selected from Import Template Step 4. Enabled for user input allowing user to override the Level 1 defined in the Import Template.
|
Pre-populated with the Level 2 that was selected from Import Template Step 4. Enabled for user input allowing user to override the Level 2 defined in the Import Template.
|
Pre-populated with the Level 3 that was selected from Import Template Step 4. Enabled for user input allowing user to override the Level 3 defined in the Import Template.
|
Related Articles
Data Import
Data Import Checklist Before importing data, you should be able to answer the following questions about the current format of your file. What type of file are you importing? Is the data normalised or pivoted? Do the data variables you wish to import ...
Automatically Import DSApp Files
You can use DataSight to automatically import the data from your DSApp Import (DSI) files. Click the Tasks button from the Automate group on the DataSight Ribbon. Click on the New button from the Quick Access Toolbar. On the invoked New Task window, ...
Import Data
Open a desired Station Table. Click Import Data. Select Manual Data Entry or Import Data File. Manual Data Entry Enter date, time and your variable value. Click Save. Import Data File Browse to your file and select Open, then click Upload. Configure ...
Video: Import Normalised Data
This video provides a basic overview of normalised data import.
Video: Import Data
This video provides a basic overview of how to import data into DataSight.