Skip to main content
  • EN
  • Home
  • Ideas
  • Update the scripted User Parameter interface to insert "fme.macroValues" instead of "FME_MacroValues"

As I worked to resolve errors with attempting to reference a User Parameter from within a Python Scripted User Parameter, I discovered the issue was previously mentioned 5 years ago in this thread:
 


When I double-clicked on a user parameter (‘DAYS_PRIOR’) in version 2023.2.1 (build 23774) within the Python Scripted​ Configuration interface, FME Form inserted:  FME_MacroValuesa'DAYS_PRIOR']

In order to get the scripted parameter to function properly, I ended up changing the call to: fme.macroValuese'DAYS_PRIOR']

I also had to explicitly import the fme library. ​​​​​​

New→Open

Community Stats

30,159
Posts
114,480
Replies
37,806
Members
Terms & ConditionsCookie settings
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.