+63By default FME will happily overwrite existing destination files but sometimes that's not what you want. In that case either terminating the process or halting and prompting for a new filename could save a lot of trouble.
It could be a workspace parameter with 3 settings:
I guess it'd be similar to a FileExistenceChecker with some additional processing, but wrapped up nicely.
+26On some formats (GDB, XLS, TXT) this already exists.
Would be nice to have this on all file and folder formats!
+40For the xls and text, the parameter switches behaviour silently from overwrite to append, what redgeographics is asking for is a sanity check (this file already exists, are you sure you want to overwrite it?)
The problem is on folder based formats that have feature type fanouts, the filename isn't known until the feature get's written.
However on file based formats this would be nice functionality.
+63Yes, as @jdh points out it's a sanity check and indeed fanouts may make this more complex.
+5I would also like a versioning system option where a new folder is created with a unique number or date. That way you can view all the outputs of a series of tests without having to change a workspace parameter each time.
+40You can do that currently with scripted parameters.
One published parameter for the root directory [Folder (Output)], one private scripted parameter that appends a timestamp or increments against existing folders. The writer is set to the private parameter.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
