Good afternoon,
I just experienced a situation that caused my workflow to stop because the source had a value that changed the datatype of a row. For instance, the table was expecting a date, but because the date was not formatted properly the SQL Writer thought that I was trying to pass a string into a date data type.
Another case were this could have been useful is when my input has orphan records from a related table. the SQL writer had an issue because the source had items that violated database relationships-- meaning there was a record that didnt exist in the parent table.
These two scenarios were painful to diagnose and currently there is no work around for them with out having to build another tool from scratch.
Thanks for the help
