Import job properties: General
On the General tab, which is present when you have opened a new or existing import job in the Import job editor, you specify the basic properties of the current import job.
Click here for information on how to edit job properties in general. And click here to read about how to manage import and export jobs.
On the current tab you'll find the following settings:
Enter the name this job should have (the name of the file that holds these settings). This name must comply with your operating system’s requirements for file names (Windows supports long file names). You don’t have to enter an extension: Designer will fill in .imp.
Enter a description of the import job, to clarify what it does.
Here you indicate how the exchange file that is to be imported is organized. For the recommended ImportTool.exe to execute the import job you create here, you can choose from:
| • | XML |
You can also import similar formats, if just the field or record separators are different.
The other formats are only supported by the now deprecated Designer import functionality and import.exe, but these tools can only be used if new database table structures like the indexed link and full text index types, the triple index type for reverse relation metadata and the metadata database table themselves are not present in your target database, because those are not supported. So preferably use ImportTool.exe or Collections, if possible.
Enter or search for the (full or relative) path and name of the exchange file that you wish to import. This name must comply with your operating system’s requirements for file names.
A relative path should be relative to the location of this import job file.
This property contains the full or relative path to the database into which you want to import data, without the name of the file. You don't have to fill in this property manually: just select a database table definition in the next option, and the path to that folder is automatically entered here. Usually, you keep your database table definitions in one folder, the \data subfolder of your Collections application folder.
A relative path should be relative to the location of this import job file.
First, enter or search for the name of the existing database table definition (an .inf file) that you wish to import the data from the exchange file into. Do not enter the extension of the file. Examples of database table names are DOCUMENT, COPIES, and Collect.
If the database that you select has datasets defined for it, these datasets will be listed in the Dataset drop-down list. (Some database tables might not have datasets though.) If you only want to import into one specific dataset in the database table, you must select this dataset.
Note that Axiell Designer (and import.exe) do not support imports into database tables with indexed link and full text index types, nor the triple index type for reverse relation metadata and the metadata database table themselves: for imports into such database tables, please use importtool.exe instead.
Feedback
