FeatureReader - different fme_basename behaviour between FME 2024.1.1 and FME 2025.2.1

You might want to check upgrading versions of Feature Reader. Here is a snapshot of 14 to 17 change log

I haven’t seen this myself, but I can see there were other transformer with expose/unexposed bugs

Can someone from Safe please check this over.

The issue is more about a change in behaviour of a workspace written in 2024 when run in FME Flow v FME form of the same version.

A workspace migrated to FME Flow 2025.2 with version 14 of the FeatureReader doesn’t return fme_basename by default when the workspace is run

Download that workspace and run it on FME Form 2025.2 without touching a single transformer and the FeatureReader does return fme_basename.

Basically in terms of backwards compatibility in this case

• Open an older workspace in a newer version of FME Form, and it will work (False)
• Take a backup of FME Flow and restore it to any newer FME Flow instance, and it will work (True)

Version 17 of the FeatureReader behaves the same way as Version 14 in 2025.2 Form in this respect, 5 FME Attributes are returned

In 2024.1 a FeatureReader only returns 3 FME Attributes if nothing additional is exposed

It's these additional attributes that can cause problems if the workspace was never previously having to handle conflicting fme_basename attributes.

Now faced with a situation that workspaces that have been regression tested after being migrated to a newer version of FME Flow won’t actually run on the corresponding version of FME Form without modification.