Is it better practice to use
import fme
param = fme.macroValues[‘parameterName’]or
import fmeobjects
param = FME_MacroValues[‘parameterName’]
in Python scripted parameters and why?
Solved
Accessing MacroValues
+28- Contributor
Best answer by daveatsafe
Hi @jdh,
FME_MacroValues is still available for backwards compatibility, but we would recommend that fme.macroValues be used instead.
I've noticed that since FME 2018 I've been getting sporadical errors when importing fmeobjects in startup and shutdown scripts on FME Server. My guess is that this is somehow related to how the server engines seem to share session objects between jobs.
So recently I've adopted the following rule, which seems to work for all my use cases.
Startup/shutdown scripts + scripted parameters
import fme
param = fme.macroValues[‘parameterName’]PythonCaller / PythonCreator
import fmeobjects
param = FME_MacroValues[‘parameterName’]It would be great if someone from Safe could chime in with the official best-practices.
+28- Contributor
david_r wrote:
I've noticed that since FME 2018 I've been getting sporadical errors when importing fmeobjects in startup and shutdown scripts on FME Server. My guess is that this is somehow related to how the server engines seem to share session objects between jobs.
So recently I've adopted the following rule, which seems to work for all my use cases.
Startup/shutdown scripts + scripted parameters
import fme
param = fme.macroValues[‘parameterName’]PythonCaller / PythonCreator
import fmeobjects
param = FME_MacroValues[‘parameterName’]It would be great if someone from Safe could chime in with the official best-practices.
jdh wrote:
That's my general rule of thumb too, but as I was preparing some training material it occurred to me that I had no real basis for that, and figured I should ask.
Hopefully Safe can give us the official explanation here.
+19- Safer
- Best Answer
Hi @jdh,
FME_MacroValues is still available for backwards compatibility, but we would recommend that fme.macroValues be used instead.
+28- Contributor
daveatsafe wrote:
Hi @jdh,
FME_MacroValues is still available for backwards compatibility, but we would recommend that fme.macroValues be used instead.
daveatsafe wrote:
Hi @jdh,
FME_MacroValues is still available for backwards compatibility, but we would recommend that fme.macroValues be used instead.
+19- Safer
takashi wrote:
Hi @DaveAtSafe, if you would recommend that fme.macroValues always be used rather than FME_MacroValues, please modify the script editor for the PythonCaller/Creator and some relevant documentations (e.g. here) in which FME_MacroValues is still used.
Thanks for catching that. I have created a problem report to have that changed to fme.macroValues instead.
1 person upvoted this
daveatsafe wrote:
Hi @takashi,
Thanks for catching that. I have created a problem report to have that changed to fme.macroValues instead.
+19- Safer
david_r wrote:
I've noticed that since FME 2018 I've been getting sporadical errors when importing fmeobjects in startup and shutdown scripts on FME Server. My guess is that this is somehow related to how the server engines seem to share session objects between jobs.
So recently I've adopted the following rule, which seems to work for all my use cases.
Startup/shutdown scripts + scripted parameters
import fme
param = fme.macroValues[‘parameterName’]PythonCaller / PythonCreator
import fmeobjects
param = FME_MacroValues[‘parameterName’]It would be great if someone from Safe could chime in with the official best-practices.
Remember, though, I'm an old school Tcl guy and Python wannabee-pretender.
david_r wrote:
I've noticed that since FME 2018 I've been getting sporadical errors when importing fmeobjects in startup and shutdown scripts on FME Server. My guess is that this is somehow related to how the server engines seem to share session objects between jobs.
So recently I've adopted the following rule, which seems to work for all my use cases.
Startup/shutdown scripts + scripted parameters
import fme
param = fme.macroValues[‘parameterName’]PythonCaller / PythonCreator
import fmeobjects
param = FME_MacroValues[‘parameterName’]It would be great if someone from Safe could chime in with the official best-practices.
+17- Contributor
daveatsafe wrote:
Hi @jdh,
FME_MacroValues is still available for backwards compatibility, but we would recommend that fme.macroValues be used instead.
I'm still seeing the legacy behavior in 2019, at least in Data Interoperability.
i.e. FME_MacroValues
+29- Contributor
daveatsafe wrote:
Hi @jdh,
FME_MacroValues is still available for backwards compatibility, but we would recommend that fme.macroValues be used instead.
Still not fixed in 2020.0
+11- Contributor
As I worked to resolve errors with attempting to reference a User Parameter from within a Python Scripted User Parameter, I discovered this thread. (Thank you, FME Community!)
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_MacroValues['DAYS_PRIOR']
In order to get the scripted parameter to function properly, I ended up changing the call to: fme.macroValues['DAYS_PRIOR']
I also had to explicitly import the fme library.
1 person upvoted this
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.