socrata
Cannot use existing control file through GUI
Unless I am missing something, one must use the "Map fields" button in the GUI. It is no longer possible to use an existing control file. This could make DataSync more cumbersome to use in some situations.
We are still on Verson 1.5.3 for our production use due to Issue #93 so I think this issue was introduced in Version 1.6 but am not sure. It exists in 1.6.1.
/CC @tomschenkjr @shua123
I wanted to resurface this issue since I was discussing it with @urmilan at Socrata Connect and it just came up in real work today. Our Data Sync update for https://data.cityofchicago.org/Buildings/Building-Permits/ydr8-5enu normally runs headlessly so I long-since have a control file for it. However, I wanted to run it through the GUI in DataSync 1.8.0 today. As far as I can tell, I cannot do so unless I go through the pretty-painful process of manually mapping 130 columns. (No, a dataset that wide is not necessarily a best practice but it is what we have in this case.)
This just came up again in a different way. The mappings in a saved job seem to be a bit fragile. That is an issue it its own right but is compounded by the fact that, even if I have a control file, I still need to remap through the GUI when the old mapping somehow breaks or disappears.