This has me stumped. I have a Workflow that has a Parameter --SourceDataset_FFS, which has got 3 Filename Path strings in it corresponding to 3 input FFS files.
The Parameter itself is of a Type: "Filename (Multiple)" with a Default value: "C:\\ArcGIS\\Water Script Working\\DEMFFS\\ELEV_DEM_1.ffs","C:\\ArcGIS\\Water Script Working\\DEMFFS\\ELEV_DEM_2.ffs","C:\\ArcGIS\\Water Script Working\\DEMFFS\\ELEV_DEM_3.ffs"
Now, running the FMW in WorkBench runs fine, and it passes to FME.exe the Parameter properly formatted by splitting the file names up at the comma delimiter by adding enclosing "" and adding spaces as such:
--SourceDataset_FFS """"""C:\\ArcGIS\\Water Script Working\\DEMFFS\\ELEV_DEM_1.ffs"" ""C:\\ArcGIS\\Water Script Working\\DEMFFS\\ELEV_DEM_2.ffs"" ""C:\\ArcGIS\\Water Script Working\\DEMFFS\\ELEV_DEM_3.ffs""""""
However, when I Batch this in another Workflow using WorkspaceRunner, it fails to run the same FMW because it complains that the file paths in --SourceDataset_FFS don't exist.
Inspecting the Log, it is because it is parsing the parameter instead as --SourceDataset_FFS "C:\\ArcGIS\\Water Script Working\\DEMFFS\\ELEV_DEM_1.ffsC:\\ArcGIS\\Water Script Working\\DEMFFS\\ELEV_DEM_2.ffsC:\\ArcGIS\\Water Script Working\\DEMFFS\\ELEV_DEM_3.ffs"
ie. Instead of recognising that it is Filename(Multiple) Parameter, it doesn't parse it properly across the commas and just joins all the file paths together in one long, non-separated string, which of course creates a malformed Path and why get the error of the path being non-existent.
Scratching my head on how to work around this? Setting the Parameter to Private didn't help and even though this meant that it didn't explicitly pass this as an FME shell argument, it still "read" the Private Parameter without the separators and get the same error, so it seems that WorkspaceRunner can't handle FMWs that use a Filename(Multiple) parameter type.
FME 2018.1