Import templates can be used to import data into one or more EnterWorks repositories. Import templates are typically created by the system administrator. When an Import template is used to import records, the only attributes that will be updated are the attributes included in the template.
To use an Import Template to import records into a repository:
- Open the desired repository in a Repository View.
-
Open the More Actions dropdown by clicking the
on the Repository View's
activity bar. The Configuration Step 1 window will appear.
-
Configuration Step 1
From the following list, select Defined Template:
-
Current View: The record attribute values are imported simply, in a delimited or spreadsheet file.
-
Defined Template: Allows the user to specify an Import Template to be used. Import Templates are typically created by the system administrator. This option will be unavailable if no import templates have been defined for this repository.
-
Create Saved Set: (Optional) This uses an imported spreadsheet that specifies a list of existing records in a repository to create a saved set in that repository. No actual record content is changed.
-
Pending Content Changes: (Optional) Select to enter changes that take effect in the future. For instructions on importing Pending Content Changes, see Batch Processing of Pending Event Transactions.
-
- On the Select Defined Template dropdown, select the Import Template to be used.
- Click Next to continue to Import Configuration Step 2.
-
Import Configuration Step 2
Edit the Options values as desired:
-
File Name: Select the file to import. The contents of this dropdown will change based on the Upload File and File on Server settings.
-
Upload File or File on Server: Select the location of the import file.
-
File Format: This option will be selected automatically based on the type of file selected above.
-
File Encoding: Select the file encoding method. You may want to leave this setting at Default, then if the data does not import correctly, contact your system administrator for help determining the correct file encoding.
-
Language: Selection of a Language here will cause any imported multi-language attributes that are not specifically assigned to a language to be imported to the selected Language. If no language is specified, the default language is used. For information about how multi-language attributes are imported, see Multi-language Behavior for Imports.
For example, if there is an attribute titled
Productand the Language selected is Polish, the column values will be imported into Product's Polish variant of the attribute values. -
Save Records Imported from Source as Set: This option will either add the imported records to an existing Saved Set or create a new Saved Set consisting of the imported records. If you select this setting, the following will appear:
- Existing Saved Set Name: Select an existing saved set. The import will add the imported records to this existing saved set.
- New Saved Set Name: Enter a name for the saved set that will be created to hold the imported records.
-
Send above Saved Set to Workflow: Set this checkbox if you want the records to be sent to workflow. This has the same effect as editing each record then clicking the Save & Send button.
-
-
Optionally, expand the Advanced Options and edit them as desired.
Advanced Options
Table 1. General Import Options
Description
File Definition Name
Deprecated.
Data Source Name
Deprecated.
Mapping Name
Deprecated.
Field Delimiter
Either select Comma, Tab, or enter the character or characters that delimit field values in the import file.
Text Qualifier
Enter the characters that indicate the start and end of a text string value.
Row Delimiter
Enter the characters that delimit rows in the import file.
Header row number
Defaults to 1.
Start at line #
Defaults to 2.
Start after line text
Enter the text that identifies the line before the start of the import records.
Stop at end of file
The default option.
Stop at line #
Instead of stopping at the end of the file, stop at the specified line number.
Stop before line text
Instead of stopping at the end of the file or at a line number, stop before reaching the entered line of text.
Table 2. Validate Import Options Import Options
Description
Non-Primary Key Data
Use a non-primary key attribute as the primary key.
Column Count
If set, this option will flag any row having a different number of columns than the header row.
Required Attributes
This option will prevent a record that is missing required attributes from being imported.
Unique Business Key (If defined in configuration)
If a business key is defined in the profile, use it as the primary key.
Column Data Type
This option will prevent a record with incorrect data types from being imported.
Table 3. Sync In Options Import Options
Description
Keep repository values if Import values are empty/null
If the import file's attribute value is empty, keep the existing attribute value instead of clearing the value.
Update Only
Only update records that already exist in repository; do not create new records.
Disallow Null Primary Keys
Ignore import record if any of its primary keys are blank.
Create Only
Only add new records, do not update any records that already exist in the repository.
Ignore white space
Ignore any extra spaces before or after the data in the import file. This option defaults to checked.
Extended Data in One Row Format
Deprecated.
Validate Afterward
After the import completes, validate the records. Allow External Trigger
Allow triggers to be processed.
Sync Scan HTML for PLT
For information about this field, contact EnterWorks.
Sync Scan XML for PLT
For information about this field, contact EnterWorks.
- Click Next to continue to Import Configuration Step 3.
-
Import Configuration Step 3
Verify the field mappings. If a file previously exported from a repository with the same profile is used and the column names were not changed, all the fields should map automatically. If any column is not properly mapped, click its column header and select the correct attribute name.
-
Taxonomy Node dropdown menu - If all Category Attributes in the input file are associated with one Taxonomy node, the Taxonomy node can be selected and only those Category Attributes will be shown for selection mapping. This is particularly useful for implementations with large numbers of Category Attributes.
-
Map Across All Taxonomies checkbox - If a field in the input file is a Category Attribute, use this checkbox to have the Category Attributes map automatically and/or show in the dropdown menu for manual mapping. Category Attributes don't show in the mapping list automatically because it could make the selection list very large.
-
Update all records on partial key matching – This checkbox is used to update multiple records based on a partial key. This option should be used with care because one record in the input file could update multiple records in the database. It is recommended that the system administrator be contacted before using this option.
-
- Click the Import button to import the data file. The Step 4: Import Configuration page will appear.
-
Step 4: Import Configuration
An Import job is created and placed in the Job Queue. To view the job's progress, open the Job Monitor from the Features sidebar's System tab or open a Job Monitor Widget in the Dashboard.The Imported record files are prepared and made available for download and transmission. Upon completion, an Import Job Completed message will appear in the Import Configuration's Step 4 window.The user can download the files created by the Import procedure by clicking the buttons below the Job Completion Status message:
-
Download Log File: Download the Import Job Log file. It contains status about the contents of the Import Job, the date and time the Import Job was run, completion status, and the number of records processed and imported.
-
The second file button is not used during imports.
-
The third file button is not used during imports.
The user can also download the resulting output files from a Job Monitor Widget.If a Saved Set was created, to view it, click the Refresh icon
on the bottom left
of the Repository View and click the Saved Set button on the Repository
View's Activity tab. The Saved Set Sidebar will appear. Click the Saved Set that
was created to see the added or modified records. -