A Data Connector import rule fails and errors occur when viewing the import rule log.
The following are some of the many possible error messages that can appear in an import rule log. Others can be found by searching the Symantec Knowledge Base for the specific error. As such, this is not an all-inclusive list. Most error descriptions are clearly defined as to why they fail, which is usually because of a logical issue from the data value or attempt to use the data in an incorrect manner. Also, some "errors" are merely warnings and can be safely ignored, as the message may simply indicating that the row was skipped because no data was present, which may be what the user intended.
Note: An error usually will mention that something is being skipped. Usually this does not indicate that the entire row will be skipped. But this depends on the context of the error. Be sure to evaluate what is in red (the problem data classes) in conjunction with what the error is stating. For example:
"Row x skipped for data class '<data_class>'. Multiple rows of data for the same resource are redundant for single-rowed data classes."
This would seem to imply that the entire row will be skipped. This is actually incorrect, in that this is only ignoring the incorrect attempts to assign multi rowed data classes to a single-rowed data class. The row is kept and updated with the remaining data classes that are not part of this. For example: If the serial number for a computer was included in two lines for the computer, where cost items are being imported, this error will occur. The first record will create the resource and add the serial number and first cost item. The second record will update the computer, skip setting the serial number (and throw the error in the log), and continue updating the remaining data classes as applicable.
How to troubleshoot import issues when using a Data Connector import rule
How to import data using a Data Connector Import Rule