Skip to main content
Solved

Getting runtime user of dynamic parameter workspace on FME Flow

  • Oct 28, 2026 11:52 AM UTC
  • 2 replies
  • 66 views

norad007
Contributor
Forum|alt.badge.img+1

FME Flow 2025.2.4.1

I have set up an FME Workspace app to run a workspace. Additionally I have set up dynamic parameter configuration to data stream the parameters from a second workbench to be used in the app and first workbench. I have added two web connections (2 separate users) to Flow. I would like the dynamic parameter workbench to use the relevant web connection based on the user who runs the dynamic workspace and parse specific parameters back to the app and first workbench. Both users are set up in flow, and prompted to login in to the app, and I am then trying to pass the FME_SERVER_RUNTIME_USER variable to filter for the right web connection. However, if the 2nd user runs the app and grabs the dynamic parameters it is always the 1st user username value (the creator/owner) and therefore the incorrect web connection.

Would anyone be able to offer any advice? How I can successfully get the runtime user of the dynamic param 2nd workspace?

A separate resource file for each user might work (Dynamic Parameter Configurations in FME Flow Apps – FME Support Center) but that’s not possible as we are on Flow 2025 not 2026.

Best answer by jeremybelcher

Hi norad007, sorry to hear about the issue. This was a bug in FME Flow 2025.2 where the dynamic parameter workspace runs as the app owner rather than the logged-in user. It’s fixed starting in 2026.2, so upgrading would resolve it in the future, but won’t help in 2025 versions.
 

To stay on a 2025 version, you can work around it by running your second workspace (the one that builds the parameters) first as its own app, which generates an HTML page. That page can then re-direct to your main workspace app, which uses Enable URL-Based Configuration to receive the values.

The workflow would be similar to this demo for chaining flow apps here: https://www.youtube.com/watch?v=99lLKukU2BA

This is also the full webinar which this was part of: https://fme.safe.com/webinars/build-smarter-web-apps-and-reduce-maintenance-with-dynamic-parameters


If you’re still running into issues with this, let me know.

 

View original

2 replies

jeremybelcher
Safer
Forum|alt.badge.img+4
  • Safer
  • Best Answer
  • Oct 29, 2026 9:56 PM UTC

Hi norad007, sorry to hear about the issue. This was a bug in FME Flow 2025.2 where the dynamic parameter workspace runs as the app owner rather than the logged-in user. It’s fixed starting in 2026.2, so upgrading would resolve it in the future, but won’t help in 2025 versions.
 

To stay on a 2025 version, you can work around it by running your second workspace (the one that builds the parameters) first as its own app, which generates an HTML page. That page can then re-direct to your main workspace app, which uses Enable URL-Based Configuration to receive the values.

The workflow would be similar to this demo for chaining flow apps here: https://www.youtube.com/watch?v=99lLKukU2BA

This is also the full webinar which this was part of: https://fme.safe.com/webinars/build-smarter-web-apps-and-reduce-maintenance-with-dynamic-parameters


If you’re still running into issues with this, let me know.

 


norad007
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • Oct 30, 2026 6:32 AM UTC

​@jeremybelcher Many thanks for replying. Ah okay at least there’s a possible work around. I will take a look and drop you a line if I get stuck. Thank you again.