Ad data inconsistency when in Staging Area and re-selected

When an ad file is Moved to Staging Area, it will display the list of data like it does in Local Files, including rows that contain a blank field. (Image1)

The data is stored in the Target DB under smb_SA Name.BA NAME_ads. When it is populating this table, if there are any rows with no text for a field, MySQL will throw an error with message "Column [column name] cannot be null" and the entire row will not be added. (Image2)

If the user selects a different Staging Area or clicks the same SA again, the data loaded into the Staging Area table is the same as data located in smb_SA Name.ads_BA NAME. (Image3)
It seems that when this happens DataLoader becomes unable to figure out which BA the data belongs to and creates a new entry with a BA ID that defaults to 0. (Image4) (id 246 is ads_alternators loaded normally, and id 247 is when loaded after re-selecting Staging Area)

Summary: File data gets pushed to Target DB with regards to what is displayed in the Staging Area tab as opposed to data located in the Staging Area schema in Target DB. Depending on if the Staging Area is reloaded or not the data that is pushed to Target DB will change.

SQL Statement at StagingAreaDriver.java line 574