Is it possible to generate a separate log file or configure the existing log file to display metadata for the reconciliation purposes.
The field that I am looking to display is the feature count in input file, feature count in both output file, who executed the workspace with timestamp, the amount field totals in the input file and the amount field totals in the 2 output files ( I have a workspace where there is 1 input file and 2 output files) . Also I have noticed that FME overwrites to the same log file every time the workspace is executed, is it possible to create a unique log file at every run?
Thank you for the support.
Page 1 / 1
Yes, you can totally generate your own custom report using the Text Writer or AttributeFileWriter, but you’ll need to collect the data you want manually within your workspace.
That means:
Counting features in your input file,
Getting the number of features written (for example, right after a FeatureWriter),
Summing up the values of your amount fields in both input and output streams,
And generating your own timestamp using a DateTimeStamper.
Regarding the user who ran the workspace: I don’t think you can get that directly in FME Form. But if you're running the workspace in FME Flow, you might be able to use system parameters like $(FME_SECURITY_USER) or $(FME_SERVER_RUNTIME_USER) to include that info.
For the log file name: You can make FME generate a unique log file for each run by enabling “Include Datetime” in Log File options under Workspace Parameters > Logging > Log File.
Hope this helps!
I did that, but it doesn't seem to be working as expected. Do you have any other tips?
I put the following in the logfile parameter box:
and it produces a Logfile in the right folder, but when it comes to the name it simply put: $(FME_MF_NAME).log
any ideas?
Hi @m_arc_o This works for me with FME 2024.2 and 2025.2 beta. Please submit a ticket via https://support.safe.com/hc/en-us/p/Support with more details about your situation.
Thank you @DanAtSafe . I’m working with Version 2024.1.2.0 (20240830 - Build 24622 - WIN64). I will try to get an update, mayby it works. If not I will submit a Ticket.
