Data Import AutoTask

Overview

This AutoTask allows you to automate Importing into Data Files.

Create the AutoTask

Note: An AutoTask requires a saved Field Mapping, so either Load an existing field mapping or Save the field mapping you create. It is also advisable to Run the Import to ensure it works as expected.

You should make selections as you would normally to Import Data. On the final, Save AutoTask page of the Import Data File Wizard, you can then click Save As New AutoTask..., saving in a Public File. You may also Use relative years to avoid having to update the source and target file years as the database environment settings change (e.g. if the AutoTask is created in 2015 and imports into 2015 WKFC then, with Use relative years selected, when the database current year is 2016 the AutoTask will automatically import into 2016 WKFC). If you are editing an existing AutoTask, there will also be an option to Save ‘the current AutoTask name’.

Run the AutoTask

When you run the AutoTask, IFP will import data into the database using all of the options previously selected, without requiring further interaction. See How to Run AutoTasks for the different ways that you can run AutoTasks in IFP.

Output tab

When you run the AutoTask the Output tab shows the results of the import i.e. how many records were imported / skipped. You can also click Save Results… to save a description of the task and the contents of the Output tab to a file.

Common Issues

There are several common issues that you may have in the creation of these AutoTasks. The main issues are highlighted here.

Incorrect Field Mapping

It is important that you use Field Mappings which relate to the data you are importing. Not having fields mapped correctly will cause problems such as not all data being imported correctly.

• Field mappings file not found indicates that the mapping file the AutoTask was using has been removed or renamed (this will also be indicated on the General tab or AutoTask Properties, highlighted in red).

• One or more field mappings are invalid indicates that columns may now have different headers in the source file, or be missing.

Selecting the renamed mapping file or editing a mapping file to reflect changes with source format can be done by editing the AutoTask.

Invalid Sheet/Table Name

If a sheet name is changed in an Excel source file, then the Output tab will indicate 'SheetName$' is not a valid name (where SheetName is the expected name of the sheet). In this case, either correct the source file or edit the AutoTask to select the new name of the sheet, as appropriate.

Target Data File Locked

In this case, the Warning Messages tab will indicate that Target data file is locked for selected period. Check if the data file has been incorrectly locked.

Incorrect File Name / Location

The error Failed to connect to the source data - file not found indicates the source file is not found at the expected location (either it has been renamed or removed). Either replace the source file, or if it has been appropriately renamed, edit the AutoTask to select the new file name.

I can't find AutoTasks in IFP

See How to Run AutoTasks for information on using AutoTasks. If you cannot access AutoTasks in IFP you may not have access rights to use them. Please contact your Local Administrator to check this.