Skip to main content
Solved

Using deployment param through scripted param UI errors off; bug?

  • March 12, 2024
  • 2 replies
  • 65 views

joaniegeo99
Contributor
Forum|alt.badge.img+2

FME(R) 2023.1.1.0 (20230928 - Build 23631 - WIN64)

I have a simple scripted parameter script in workbench to return the value of a deployment parameter and I’m wondering if there’s a bug in the interface. When I drag a user parameter onto the script canvas the code generated contains FME_MacroValues, eg.

FME_MacroValues['SomeUserParam']

If  I drag a deployment parameter, dpTest, onto the script canvas the code generated looks like

$(dpTest)

Here’s the script. The commented code fails; if I manually correct $(dpTest) to FME_MacroValues['dpTest'], it runs:

 

# Get the archive folder from deployment param
import fme

#arch = $(dpTest)
#return arch

return FME_MacroValues['dpTest']

 

Is this a bug? Thanks.

Best answer by mattmatsafe

Hi @joaniegeo99, thanks for reporting this! It is indeed a bug. We’ll get that fixed for a future release of FME. The workaround, as you’ve already found, is to manually correct the parameter format in the script. Apologies for any confusion and inconvenience this caused.

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.

2 replies

mattmatsafe
Safer
Forum|alt.badge.img+14
  • Safer
  • 108 replies
  • Best Answer
  • March 18, 2024

Hi @joaniegeo99, thanks for reporting this! It is indeed a bug. We’ll get that fixed for a future release of FME. The workaround, as you’ve already found, is to manually correct the parameter format in the script. Apologies for any confusion and inconvenience this caused.


mattmatsafe
Safer
Forum|alt.badge.img+14
  • Safer
  • 108 replies
  • August 5, 2024

Please note that this has been fixed in FME 2024.1 b24555+