BatchUploader date question + serverside parsing bug

[Blama]

Hi Isomorphic,

please see this sample (happens in latest 5.1 and the 6.0 online showcase) and upload this file:

"nextShipment","category","itemName","itemID","unitCost","description","SKU","inStock","units"
"11/21/2014","Audio","Small grey widget",,0.41,"","545315","","Ea"
"21/11/2014","Audio","Small grey widget",,0.41,"","545315","","Ea"
"2014/21/11","Audio","Large grey widget",,0.41,"","45300","","EACH"
"2014/11/21","Pencils","Small blue gizmo",,-0.47,"","90600","","Ea"
"2014-11-21","String","More string",,0.58,"","1900111","","Roll"
"2014-21-11","String","More string",,0.58,"","1900111","","Roll"

Please see that the 1st four rows have errors in the date field.
After double clicking the field and leaving the editRow again, 1+4 are valid dates now. 3 suffers from this bug.
6 is successfully parsed, but not formatted(?). (2 has a genuine error and 5 is OK).

In the server logs for the upload, the rows with errors have Translater exceptions.
It seems that the parsing on the client is more lenient than on the server.

Besides the bugs:
What is the expected date format for BatchUploader? Is it (Browser) locale-setting dependent?

Thank you & Best regards
Blama

[Isomorphic]

The server expects a fixed format of yyyy-mm-dd and assumes dates should be parsed in the server's timezone. Currently this is not configurable, so custom code would be required to do something different - your uploadDataSource would need to do parsing and place Date instance in the data. We're still looking at the issue where some rejected dates are not being flagged properly as validation errors.

[Isomorphic]

We've made a change to address the issue where some rejected dates are not being flagged properly as validation errors. Please try the next nightly build, dated June 22.

Regards
Isomorphic Software