I'm curious, why do you need this? For most systems it shouldn't make any difference.
Hi @annmarie, a possible workaround is to write the resulting tif files into a temporary folder with the FetureWriter at first, and move them with file name containing capital extension to the final destination folder with the File Copy writer.
[Addition] Instead of the pair of VariableSetter/VariableRetriever, you can also use the FeatureMerger to merge the temporary path to the raster features unconditionally.
Hi @annmarie, a possible workaround is to write the resulting tif files into a temporary folder with the FetureWriter at first, and move them with file name containing capital extension to the final destination folder with the File Copy writer.
[Addition] Instead of the pair of VariableSetter/VariableRetriever, you can also use the FeatureMerger to merge the temporary path to the raster features unconditionally.
Hi @annmarie, a possible workaround is to write the resulting tif files into a temporary folder with the FetureWriter at first, and move them with file name containing capital extension to the final destination folder with the File Copy writer.
Addition] Instead of the pair of VariableSetter/VariableRetriever, you can also use the FeatureMerger to merge the temporary path to the raster features unconditionally.
rename @Value(_pathname)\*.ini *.INI
That way you won't have to use a temporary file location and the filecopy writer.
Hi @annmarie, a possible workaround is to write the resulting tif files into a temporary folder with the FetureWriter at first, and move them with file name containing capital extension to the final destination folder with the File Copy writer.
[Addition] Instead of the pair of VariableSetter/VariableRetriever, you can also use the FeatureMerger to merge the temporary path to the raster features unconditionally.