To run a Create a Saved Set import:
- Open the desired repository in a Repository View.
-
Open the More Actions dropdown by clicking the
on the Repository View's
activity bar.
- Select the Import option. The Import Configuration Step 1 window will appear.
-
On the Configuration Step 1 window, for the Import Type,
select Create Saved Set from the following list:
-
Current View: The record attribute values are imported simply from a delimited file or spreadsheet.
-
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) Use 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.
-
- Click Next to continue to Import Configuration Step 2.
-
The Import Configuration Step 2 window will appear. Edit the
Option values:
-
File Name: Choose the file to import. This file must be a spreadsheet that consists of the
-
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: If the name of a multi-language attribute in the import file does not indicate the language variant of the attribute it should be imported into, the Language selection specifies which language variant the value will be imported into. For information about how multi-language attributes are imported, see Multi-language Behavior for Imports.
-
Save Records Imported from Source as Set: This option will be automatically selected. Select which of the following to use:
- Existing Saved Set Name: Select an existing saved set. The import will add the specified records to this existing saved set.
- New Saved Set Name: Enter a name for the saved set that will be created to hold the specified 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.
-
- Click Next to continue to Import Configuration Step 3.
-
Verify the input records' attribute 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.
A Primary Key indicator (blue key) will appear next to the name of the attribute that has been determined to be the primary key.A Confidence Indicator is displayed next to each attribute name:
-
Green box with green check mark: Confidence is high that this attribute has been properly mapped.
-
Green box: Request for confirmation that this attribute was properly mapped. To confirm, click the green checkbox.
-
Red X: This attribute has not been mapped.
-
- If any column is not properly mapped, click its column header and select the correct attribute name.
-
Edit the rest of the configuration options.
-
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.
-
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 any Job Status Files created by the Import procedure by clicking the buttons below the Job Completion Status message:
-
Log File: Download the 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.
-
Output File: Not used during imports.
-
Error File: May or may not be created.
The user can also download the resulting Job Status 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 Saved Set 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
- Click the Refresh icon