Import warning messages and actions you can take

Before the import begins, warning messages are listed. You can take actions to remove the messages or proceed to import without resolving the warning messages.

Use Table 1 to determine if you want to remove messages before importing or proceed to import without removing the messages.

The left column shows warning messages that can be listed in the preview pane and provides additional information to help you to understand the message.
The center column lists corrective actions you can take to remove the message. You can choose one or more of the actions listed.
The right column describes what happens if you do not take corrective action and proceed to import.

Table 1. Warning messages
Messages and additional information	Take action to remove messages	Ignore the messages and proceed
The source column {name} could not be resolved. A candidate column was created. The target column {name} could not be resolved. A candidate column was created.	Perform one of the following actions: Correct the data source names in the .csv file. Use Name to Omit from the Multipart Data Source Name to omit the part of the name that does not resolve. Do not select Case sensitive matching for data source names and then proceed. The columns are matched and mapped to existing data source names. Note: An imported mapping can map to the wrong data source, if the metadata repository contains two data sources with names that are similar and that differ only in the use of letter case.	The imported mapping specification includes cells that contain candidate columns that you can use to create a model or that you can replace with columns that exist in the metadata repository.
The source term {name} could not be resolved. A candidate term was created. The target term {name} could not be resolved. A candidate term was created. Additional information: The .csv file contains terms that do not match terms in the metadata repository.	Correct the terms in the .csv file.	The imported specification includes cells that contain candidate terms that you can use to create a model or that you can replace with terms that exist in the metadata repository.
Multiple matches were found for {name}. The first match is assumed. During import, multiple matches were found. The first match {name} was chosen. Additional information: Case sensitive matching for data source names is not selected. If you do not use this check box, an imported mapping can map to the wrong data source if the metadata repository contains two data sources with names that are similar and that differ only in the use of letter case.	Perform one of the following actions. Correct the data source names in the .csv file. Select Use full multipart data source name to obtain an accurate match. Select Case sensitive matching for data source names and then proceed. Data sources names in the .csv file that match the character string and letter case of data source names in the metadata repository are mapped and imported. Unmatched data sources names are imported as candidate columns.	The imported mapping specification includes mappings that map to existing data sources. Verify the mappings after the import.
Lookup {name} uses candidate tables. The lookup will not be imported.	Perform one of the following actions. Correct the data source names in the .csv file. Select Use full multipart data source name to obtain an accurate match. Select Case sensitive matching for data source names and then proceed. Data sources names in the .csv file that match the character string and letter case of data source names in the metadata repository are mapped and imported. Unmatched data sources names are imported as candidate columns.	Lookups that use candidate tables are not imported.