I've search and searched for a way to do this, but no method seems to work. Basically I want to use the input feature class name (feature type in FME) as the output name. This normally works, however the tool I'm using (ChangeDetector) adopts the "revised" input as the output Feature name instead of the "original" input name. Even linking the "original" input name to the output name attribute does not work. It keeps the "revised" input name. I've tried using various transformers like the SubstringExtractor to pull the name and set the writer to fan out by this attribute, but even that fails.
While I would prefer to get this working within the workbench, I do plan on using this workbench in a python script, so it would be handy to get it working through that as well. I setup the workbench to run using
subprocess.Popen(["pathToFme", "pathToWorkbench"])
This works just fine. Subsequently I tried adding parameters at the end, to input the name based on code samples I found while searching this...
subprocess.Popen(["pathToFme", "pathToWorkbench"] --fileName: "nameOfOutput")
with "fileName" being the name of the parameter within the workbench, but I can't seem to get it to run, let along pick up the parameter input from the script. I couldn't get os.system to properly execute the workbench, so I want to stay away from that.
Basically what I am trying to achieve is the ability to take a large number of inputs, run them through the changeDectector, and output with the same name as the "original" input.
Any help or suggestions would be appreciated. Thanks.