levyj
commented
11 years ago This could be another way to get at a problem I had this morning (my fault; forgot the DS rules). A column did not import because the header did not match the existing column name in the dataset. I was going to suggest allowing some sort of translation/mapping option in DS and that still might be useful, although complex. The advantage it potentially could have is cutting down on necessary manipulations of the input file before loading it. Sometimes it comes from an external system beyond our control and the headers and column orders are what they are. If at least one (order or names) does match the target dataset, it would be nice not to have to make changes before loading.
As an add-on to this enhancement, maybe have a check box that basically says, "There is a header row present but ignore it." That would have handled this morning's case where my columns were in the right order but there was a header row with a mismatched name.
alaurenz
DataSync should give the user the option of uploading a CSV file without column headers. Have a checkbox to user checks to tell DataSync their CSV does not contain a column header row. If this box is checked DataSync should refer to the order of the columns in the CSV.
It might also be useful to give the user feedback in the UI if the column headers of the CSV file (or lack thereof) does not match that of the dataset.