Skip to main content
Question

Dynamic Workspace Parameter fails after upgrading FME Flow from 2025.2 to 2026.2

  • July 28, 2026
  • 3 replies
  • 65 views
felix.pekarek
Contributor
Forum|alt.badge.img+2

Hi everyone,

After upgrading our FME Flow instance from 2025.2 to 2026.2, a workspace parameter with dynamic values stopped working in a Workspace App.

When opening the app, FME Flow shows the following error when testing the dynamic parameters:

Loading from Workspace
Kartenautomatisierungen/Kartenautomatisierung_ZUBA_PreScript_2.fmw

Error loading schema

Unable to generate dynamic parameters from source file.
Error was:
E:\appdata\fme\systemshare\resources\system\null\null\FeatureWriter\ZUBA.json

Please ensure the file exists and is readable.

 

A few observations:

  • The same setup worked without issues in FME Flow 2025.2.
  • The workspace itself executes successfully. It loads the JSON after the workspace is done. 
  • The error only occurs while loading the dynamic workspace parameter.
  • The path contains system\null\null\FeatureWriter\ZUBA.json, and the corresponding folders do not exist.
  • I never configured FME to write schema files to that location.

Has anyone seen a similar issue after upgrading to 2026.2? Is this a known problem with dynamic workspace parameters or FeatureWriter based schema generation?

There is a known issue (FMEFLOW-27717) regarding this, which should be resolved in 2026.2 but I still get this error.

    3 replies

    hkingsbury
    Celebrity
    Forum|alt.badge.img+74
    • hkingsburyCelebrity
    • Celebrity
    • July 29, 2026

    I wonder if there may be a slight change in the backend of dynamic parameters between the two versions that's causing this issue.

    If you make a new workspace app (or maybe just recreate the dynamic parameter in the existing app) does that resolve it?

    felix.pekarek
    Contributor
    Forum|alt.badge.img+2
    • felix.pekarekContributor
    • Author
    • Contributor
    • July 29, 2026

    I already tried that as well because I had the same suspicion. Unfortunately, it did not resolve the issue.

    I tested both duplicating the workspace and creating a completely new workspace from scratch, but neither approach helped. I also removed all existing published workspaces from FME Flow and uploaded them again, however the problem persists.

    felix.pekarek
    Contributor
    Forum|alt.badge.img+2
    • felix.pekarekContributor
    • Author
    • Contributor
    • July 31, 2026

    The issue was resolved after reinstalling FME Flow. It looks like the original deployment by me may have been faulty. Thanks for your help and suggestions! 😊

      Community Stats

      32,832
      Posts
      124,489
      Replies
      41,390
      Members
      Terms & ConditionsAccessibility statement
      A product of
      Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.