Skip to main content
Released

Common Parameters

Related products:FME Flow
  • February 1, 2023
  • 7 replies
  • 41 views

jdh
Contributor
Forum|alt.badge.img+40

It would be very useful if FME could manage common parameters in a similar way to Database or Web Connections.


Many of our workspaces use the same (private) parameters, when authoring a new workspace we need to recreate or copy the parameters over from an existing workspace. If the value of that parameter changes, then every workspace needs to be edited, whereas with a web connnection one can simply edit the connection in FME options once, and be done.


This can also simply the moving of a workspace though the different DEV, STAGE, PROD environments in FME Server. A common issue we have is a private parameter that points to an internal REST API endpoint, and of course we have different endpoints for the different environments, and that parameter does not always get updated when promoting workspaces to the prod server. To prevent this, the "named parameter connection" would be pre-defined on the different FME servers with the appropriate data, and the workspace would remain unchanged between environments.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

7 replies

stewartatsafe
Safer
Forum|alt.badge.img+9

We are actually working on a new feature for FME Server 2023.0 called the Deployment Parameter Store which will enable exactly this. Watch this space!


jdh
Contributor
Forum|alt.badge.img+40
  • Author
  • Contributor
  • February 1, 2023

Will it just be for server, or will desktop without server also work?


stewartatsafe
Safer
Forum|alt.badge.img+9

You need FME Server. You create the parameters on FME Server, in FME Desktop you can then sync to the FME Server pulling all the parameters down. You can then use these deployment parameters throughout the workspace. When you run the workspace the deployment parameters will automatically resolve on each FME Server using the values defined in each environment, e.g. DEV, STAGE, PROD.


jdh
Contributor
Forum|alt.badge.img+40
  • Author
  • Contributor
  • February 1, 2023

While that will certainly be a very useful improvement, there is still a good case for common/shared parameters in FME Desktop.


chriswilson
Enthusiast
Forum|alt.badge.img+21
  • Enthusiast
  • May 31, 2023

Similar to this as well, though the released status of the linked idea(s) here relates more to FME Flow (formerly Server) than Form (Desktop):

https://community.safe.com/s/bridea/a0r4Q00000HbsKaQAJ/richer-user-parameters-prompt-ui?currentpage=1


LizAtSafe
Safer
Forum|alt.badge.img+18
  • Safer
  • March 25, 2024
In DevelopmentReleased

LizAtSafe
Safer
Forum|alt.badge.img+18
  • Safer
  • June 15, 2024
https://support.safe.com/s/article/Deployment-Parameters