+20I need these translation log info to be part of my translation canvass so I can include them into the header of my report.
I used to have this solution in place but I'm hoping to find a more efficient way to include the info in my canvass and not the shutdown.
Best answer by salvaleonrp
Hi @Renato Salvaleon,
The LogMessageStreamer transformer won't return the first lines in the log file, so your best bet is to add a FeatureReader triggered by a feature close to the end of the workspace. Read the log file as a Text File.
You can get the location of the logfile by concatenating the FME_MF_DIR and FME_MF_NAME parameters, then replacing the '.fmw' at the end with '.log'.
I like that, no need for the shutdown script.
+19Hi @Renato Salvaleon,
The LogMessageStreamer transformer won't return the first lines in the log file, so your best bet is to add a FeatureReader triggered by a feature close to the end of the workspace. Read the log file as a Text File.
You can get the location of the logfile by concatenating the FME_MF_DIR and FME_MF_NAME parameters, then replacing the '.fmw' at the end with '.log'.
+20Hi @Renato Salvaleon,
The LogMessageStreamer transformer won't return the first lines in the log file, so your best bet is to add a FeatureReader triggered by a feature close to the end of the workspace. Read the log file as a Text File.
You can get the location of the logfile by concatenating the FME_MF_DIR and FME_MF_NAME parameters, then replacing the '.fmw' at the end with '.log'.
I like that, no need for the shutdown script.
+20I like that, no need for the shutdown script.
Thanks @daveatsafe, exactly what I needed.
Worked for me. I just have to expose the attribute text_line_data and do some string parsing and I get the results I need.
