While users with sufficient permissions can create and edit import templates, it is recommended that the system administrator verifies and tests them to make sure they work correctly. Import templates should be tested with one or two records on your development environment before using them on your production system.
The configuration options are the same for creating and editing import templates. The only difference is in how the Manage Import Template editor is opened.
To create or edit an import template:
-
Open the Import Template tab: Open the Feature Sidebar, open the Administration folder, open the Templates folder, and select Import Template.
- To create an import template, click the Add button in the Import Template tab's activity bar. A new import template will open in the Manage Import Template editor tab. The Manage Import Template editor tab will initially contain only the Details page, however, after you enter the required fields in the Details page and click the Save and Continue button, the remaining Manage Import Template editor pages will appear and all the pages can be edited as described in the following steps.
- To edit an existing import template, select the import template and click the Edit button in the Import Template pane's activity bar. The import template will be opened in the Manage Import Template editor tab.
- The Manage Import Template editor has three pages of configuration options: Edit the configuration options as desired.
- To save your changes to the import template, open the Attribute Mapping page of the Manage Import Template editor and click Save. For changes to Related Repositories to be saved, at least on attribute must be mapped.
Details
The Manage Import Template editor opens in the Details page, which contains the following configuration settings:
-
Name: (Required) The name of the import template. This field can support multi-language translations.
-
Description: (Optional) A description of the import template. This field can support multi-language translations.
-
Root Repository: The top-level repository that values will be imported into. Once the Details page has been saved for the first time, this field cannot be changed.
-
Type Code: Standard or Category as defined below. Once the Details page has been saved for the first time, this field may no longer be changed.
Option Advantages Disadvantages Standard (All versions of EnterWorks.) Able to use VTL scripts or triggers to alter records that have been imported. Default system configuration limits an import file to 1000 columns or less (depending on the data types of the columns). The limit can be changed by modifying the max.file.download.sizeshared configuration property.Category (Enable 9 and later only.) Able to import files with a virtually unlimited number of columns. (Typically, in files with a large number of columns, most columns are mapped to category attributes.) Not able to use VTL scripts or triggers to alter records that have been imported. Also, you can only import into a single repository.
-
Advanced Import Class Path: Specifies a class path for the JAVA class that will be invoked upon using the import template. This only appears if Type Code is Standard.
-
Contents Replacement: If the Contents Replacement checkbox is marked, all records in the root repository will be replaced with the imported records. This option will not appear the first time the Details page is saved. Also, it is only available if the import only affects the root repository. No linked repository records can be replaced.
Warning: This option should be used only if you want all repository records to be deleted and replaced with the imported data.To use the Contents Replacement function, the repository must include a status attribute that will be used to mark records that existed in the repository prior to the import but were not replaced with a record from the import file. This status attribute is defined with the special function indicator of Status. The value indicated in Inactive Status Value is entered into the status attribute in records that were not replaced.
- Inactive Status Value: (Required if Contents Replacement is checked): Defines the value to be entered in the status attribute used to indicate records that were not replaced when a file was imported. This only appears if Contents Replacement is marked.
Edit the Details page's configuration options as desired. Click Next to continue to the Related Repositories page.