Create a fileView on top of files/tables that have annotations (a1,string), (a2, int) for example.
Download results of query over view
Update the results, put a string where there should be an int (i.e. in a2)
Upload the results
==> Error '<p>syn11424654 (ILLEGAL_ARGUMENT): For input string: "A"</p><p>syn11424657 (ILLEGAL_ARGUMENT): For input string: "D"</p>'
The error is correct (I did put 'A' in a2 which was int) but unfriendly.
Note: The preview correctly typed the a2 column, I chose to ignore it. Maybe we should point it out and ask for confirm before uploading?
Per once the user sees the error message they tend to retry their batch of changes, redoing updates that actually worked which, in turn generates a conflict. So addressing this issue requires thinking through the larger user workflow.