Required Fields should throw an error when missing, right?
Rod asked 6 years ago
We were expecting Smart Connect to throw an error if a required destination field was blank. However, no error was thrown.
The value inside of a required field was blank and no length.
A CSV file is the data source. A SQL table is the destination. Smart connect shows, inside of the mappings, which fields are required (matching the primary key restraints inside of SQL).
The row of a CSV had a blank value. All other fields in the same row had values. The row was, obviously, NOT inserted into the SQL table. Yet, no error occurred inside of smart connect. It was just skipped.
Has anyone experienced this?
Thanks
The value inside of a required field was blank and no length.
A CSV file is the data source. A SQL table is the destination. Smart connect shows, inside of the mappings, which fields are required (matching the primary key restraints inside of SQL).
The row of a CSV had a blank value. All other fields in the same row had values. The row was, obviously, NOT inserted into the SQL table. Yet, no error occurred inside of smart connect. It was just skipped.
Has anyone experienced this?
Thanks