This AutoTask allows you to import item codes into a database using an automated process, or to step through the manual process with predefined selections.
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 Item Codes. On the final Save AutoTask page of the Item Codes Import wizard, you can then click Save As New AutoTask..., saving in a Public File.
Run the AutoTask
When you run the AutoTask, IFP will import item codes 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.
When run via AutoTask Manager, 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, the contents of the Output tab and any warning messages, to a file.
Warning Messages tab
This displays any warning messages generated during the import. For example, it will show why an item code could not be imported.
There are some common issues that you should be aware of when creating and running an AutoTask for Importing Item Codes:
Incorrect Field Mapping
It is important that you use Field Mappings which relate to the item codes you are importing. Not having fields mapped correctly will cause problems such as not all item codes 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.
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.