In the screendump it looks like the CSV-file always have the same structure. There is an option 'Field names follow header' that is turned of. It might be the solution to turn it on.
I know that the Excel reader has an option to 'Apply current settings to additional files', but one is not available for CSV files. Also the CSV Reader has significantly changed in 2017, maybe that will solve your problem as well.
In the screendump it looks like the CSV-file always have the same structure. There is an option 'Field names follow header' that is turned of. It might be the solution to turn it on.
I know that the Excel reader has an option to 'Apply current settings to additional files', but one is not available for CSV files. Also the CSV Reader has significantly changed in 2017, maybe that will solve your problem as well.
I've tested with the "Field names follow header' selected too and it made no difference. Also played with the Header Lines to Skip parameter and that didn't help either. It seems like the CSV Workspace Resource is completely ignored by the Generic reader.
Hi @rkay,
we were able to reproduce this issue and it looks like FME 2017 does not handle the Workspace resources, that were created in FME 2016, correctly. I filed a report to fix this and will let you know as soon as we have an update on this.
A possible workaround, for now, would be to open the workspace in FME Desktop 2017, remove the Workspace Resource and add the CSV Workspace Resource again. Now the workspace should work as expected once you publish it to FME Cloud.
Thanks for reporting this!
UPDATE:
This is currently not planned to be fixed, but here is another possible workaround:
Use 2016 to change the GENERIC reader's input format to CSV. Then, even when run with 2017 or later, the reader format and the workspace resource format will match.
