In FME 2019, the option exists to use the Data Inspector when the Visual Preview Window is closed.
But running a workspace from a batch file, the Data Inspector is not opened, even though the output is to an Inspector transformer.
Running from batch should consider the Preview Window closed and always use the Data Inspector for output through Inspector transformers.
+17This issue (not opening the FME Data Inspector when the workspace is run from batch) causes a lot of my validation workspaces not to show the invalid data even though the data is sent to the Inspector transformer.
I use batch files to run these workspaces.
+17Suggested solution:
Add this checkbox option to the Translation tab in FME Options:
Disable Inspector transformers at Runtime (Yes/No)
That would allow us to use Inspector transformers as output when using a batch file.
+5Why don't you use a FFS writer and a second line to launch the Inspector exe on your output?
+18@erik_jan The work-around since FME 2019 is to add --FME_LAUNCH_VIEWER_APP YES
to your command. (The default is NO.) Unfortunately this hasn't been documented yet.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
