When using a Data Connector import rule, the data to import includes a blank (null) value for an existing record's column value. For example, a computer's System Number field is desired to be blanked by setting its value to null via the data file. This may look like the following:
Name, System Number, Comment
PC1,,This PC was changed on 9/1/2013
Where ",," is the blank System Number column value.
When the import rule runs, however, this fails to blank the specified column, instead skipping this and returning the error "x rows of data were skipped for data class '<column_name>'."
In the Connector Rule Rule Status window:
x rows of data were skipped for data class '<column_name>'.
In the Import Rule Log Viewer window:
Row x skipped for data class '<column_name>'. All columns contain null values.
The column contains a blank value, which Data Connector ignores.
This is working as designed. Data Connector is only designed to import data as valid characters. A blank or any number of only spaces, effectively making it null, is not a valid character(s) to import.
There are two ways to change this functionality:
Data Connector import rule fails to import fields as null when they are double quotes
How to troubleshoot import issues when using a Data Connector Import Rule
Any version of Data Connector Solution.