Hi @jdh
Is this using FME Server 2017?
I have had the same issue using the $(FME_SERVER_SHAREDRESOURCE_DATA) as a destination folder.
That too adds the folder to the ZIP download.
Hi @jdh
Is this using FME Server 2017?
At the moment, I'm using 2016, but I will be upgrading to 2017.1 in August (assuming it's released).
I have had the same issue using the $(FME_SERVER_SHAREDRESOURCE_DATA) as a destination folder.
That too adds the folder to the ZIP download.
And I noticed this in FME Server 2016 and 2017.
Hi @erik_jan and @jdh
I think I may have an answer, shown as images:
In workbench:
Result of the download (unzipped):
Some more findings:
If I leave dest destination folder empty, or assigned to a parameter it gives me the folder called 'dataset' within the zip folder and then all of the data.
If in workbench I set the destination directory to Desktop (for example) it goes zip > Desktop > data (instead of zip > dataset > data). It always seems to pick up the last folder in the path to use as the top level folder.
If I set the output director in workbench to just be a . (working directory) it goes zip > folder (named the same as zip file) > data
Hi @erik_jan and @jdh
I think I may have an answer, shown as images:
In workbench:
Result of the download (unzipped):
Some more findings:
If I leave dest destination folder empty, or assigned to a parameter it gives me the folder called 'dataset' within the zip folder and then all of the data.
If in workbench I set the destination directory to Desktop (for example) it goes zip > Desktop > data (instead of zip > dataset > data). It always seems to pick up the last folder in the path to use as the top level folder.
If I set the output director in workbench to just be a . (working directory) it goes zip > folder (named the same as zip file) > data
For some reason I had to recreate the workspace from scratch, but putting " ." in the fanout dir is now producing a zip file with the desired folder structure.