+17Hi there,
Just finished a fresh install of FME Flow 2025.2.1.
I was configuring the backups and noticed that the output files were not getting a timestamp.
Looking at the httpcallers they both submit using the non-timestamped attribute:
If Append Date is No:
If Append Date is yes:
What it should be:
Thanks,
Marc
+5Hi
I was wondering what FME Form version you are using. Is it the same version as FME Flow?
Based on the screenshots, it appears that the actual value of packagePath is not automatically updated when you set 'append date' to 'yes'.
However, I could see the _timestamp attribute under the FME Feature Attributes. I would recommend concatenating the original path and timestamp and checking if that works.
Cheers,
Skyler
+17Hi
I was wondering what FME Form version you are using. Is it the same version as FME Flow?
Based on the screenshots, it appears that the actual value of packagePath is not automatically updated when you set 'append date' to 'yes'.
However, I could see the _timestamp attribute under the FME Feature Attributes. I would recommend concatenating the original path and timestamp and checking if that works.
Cheers,
Skyler
Hi,
Yes I have also install the latest version of FME Form, so they match.
I can also see the timestamp attribute, and the concatenated attribute already exists in the workspace, as per my third screenshot. It is created in the bookmarked part of the flow just out of my screenshot. I think that this is an error in the workspace that is supplied with FME Flow. Safe should correct the attribute and replace this in future versions of Flow.
Thanks,
Marc
+5Hi
This definitely seems like an error with the Utilities/BackupConfiguration.fmw workspace in 2025.2.1 - I’ve reported this to our Development team (reference FMEFLOW-27189).
I’m glad you were able to get the workspace working despite this mistake. Let us know if there’s anything else we can help with!
Thanks,
Zoe
